-
Notifications
You must be signed in to change notification settings - Fork 145
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
code
and message
is the same in JSON output
#1287
Comments
Since @EnTeQuAk and I discussed moving to the eslint standard of using the rule name to replace |
Correct, it's a bit of a tricky problem. We do have We do have the ability to overwrite |
I'm looking to filter for specific codes to filter under programmatic usage. Can I pass a flag that's like "this isn't eslint, give me generalized codes"? |
Please add some STRs to this bug or mark it as "qa: not needed" |
Describe the problem and steps to reproduce it:
Get results from programmatic usage of the linter (as an API)
What happened?
In results, the
code
field of warnings is the same thing as themessage
field. example:What did you expect to happen?
The
code
field that would be something like "UNSUPPORTED_API", as listed in the messages definition:addons-linter/src/messages/javascript.js
Line 266 in 286ebbc
Anything else we should know?
Nah.
The text was updated successfully, but these errors were encountered: