-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error after upgrade to 1.6.2 #450
Comments
Same here, different error through a Grunt linting task: |
I have just executed the unit test for this rule, and do not have any errors. I will ublish a the 1.6.3 release this afternoon with a fix for #454 . Can you test again with this new version ? |
1 similar comment
I have just executed the unit test for this rule, and do not have any errors. I will ublish a the 1.6.3 release this afternoon with a fix for #454 . Can you test again with this new version ? |
@Gillespie59 sorry for the delay, I'll ask someone in my team to test it and we'll update here. Thanks for your work 😃 |
This has been fixed in the current eslint version. It now supports for both rules with a See https://github.com/eslint/eslint/blob/master/lib/eslint.js#L867 |
Hello, I work with @elamperti, we have tested version 1.6.3 and seems that it solved the issue, the eslint version we are using is the |
So I can close this issue? |
I close the issue. You can reopen it at any time |
I have the same issue.
if I try add 'angular' to
there are error
|
generally, through these 20 days, I didn't find a solution, also it was an old repo on angular 1.5, so it's not so important already, but if it will be possible to fix this error - it helps work with old repos in future and update them or rewrite ... never mind. I resurrected two abandoned npm packages at least to start it with updated dependencies :) so ... |
Warning: Error while loading rule 'angular/angularelement': ruleCreator is not a function
Seems like plugin is loaded after the rule is attempted to be retrieved.
The text was updated successfully, but these errors were encountered: