-
Notifications
You must be signed in to change notification settings - Fork 934
"scope-empty": [2, "always"] is triggering an error when it shouldn't #10
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
Labels
Comments
Thanks for the report! Adding a regression test and fixing the problem right now. |
marionebl
added a commit
that referenced
this issue
Aug 15, 2016
* add related regression tests * default to "never" keyword * correctly negate rule result and message for "always" closes #10
marionebl
added a commit
that referenced
this issue
Aug 15, 2016
* add related regression tests * default to "never" keyword * correctly negate rule result and message for "always" closes #10
marionebl
added a commit
that referenced
this issue
Jul 7, 2017
* add related regression tests * default to "never" keyword * correctly negate rule result and message for "always" closes #10
marionebl
added a commit
that referenced
this issue
Jul 10, 2017
* add related regression tests * default to "never" keyword * correctly negate rule result and message for "always" closes #10
marionebl
added a commit
that referenced
this issue
Jul 10, 2017
* add related regression tests * default to "never" keyword * correctly negate rule result and message for "always" closes #10
marionebl
added a commit
that referenced
this issue
Jul 11, 2017
* add related regression tests * default to "never" keyword * correctly negate rule result and message for "always" closes #10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This commit has no scope. However, I am getting an error:
The text was updated successfully, but these errors were encountered: