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.
Description
Added a new output format called
pylint-parseable
that follows this format:{path}:{line}: [{msg_id}({symbol}), {obj}] {msg}
.Updated a comment in the existing pylint formatter to reflect the actual formatting generated by the formatter and updated the docs accordingly.
Related Issue
Motivation and Context
When trying to integrate prospector into a CI/CD tool I realized that the pylint output does not follow the same output format as when using
pylint --output-format=parseable
(see Pylint 3.3.3 Documentation The existing format includes the character in the output which makes it difficult for it to be used as a drop-in-replacement. I added a new formatter that uses the format mentioned in the docs. I added a new formatter to avoid make a breaking change.How Has This Been Tested?
Since this does not affect other areas it was only tested using some existing python projects to test the output.
Types of changes
Checklist: