Add "rule" attribute to "lintxml" output format #409
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Summary: Currently, there's no way to determine which rule generated a lint message if you have a parser on top of CSSLint. Provide a `rule` attribute which has the rule ID. (The specific motivating use case is that I have a program which runs multiple linters, manages lint message severity above the linter level, and has more severity levels than CSSLint itself does, so using flags like `--ignore` would require special casing and reduce flexibility.) Test Plan: Added new test coverage and executed unit tests.
This was referenced Aug 23, 2013
|
+1 |
|
+1 |
XhmikosR
added a commit
that referenced
this pull request
Jan 9, 2016
Add "rule" attribute to "lintxml" output format
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary: Currently, there's no way to determine which rule generated a lint
message if you have a parser on top of CSSLint. Provide a
ruleattributewhich has the rule ID.
(The specific motivating use case is that I have a program which runs multiple
linters, manages lint message severity above the linter level, and has more
severity levels than CSSLint itself does, so using flags like
--ignorewouldrequire special casing and reduce flexibility.)
Test Plan: Added new test coverage and executed unit tests.