Parse output messages using custom format #7
Conversation
This file contains 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
Allows for more control and fixes issues with outputs not recognized by the regex
ROpdebee
force-pushed
the
ROpdebee-change_output_format
branch
from
9ce83c2 to
23a9a30
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allows for more control and fixes issues with outputs not recognized by the regex. Previously this linter plugin's status would be displayed as erred all the time because of unrecognized messages, even when no actual errors/warnings were produced, because of logging output to stderr and summary statistics printed after checking the file. Using this custom format the summary output can be prevented, and it simplifies the regex too.
Note: Will require Bandit >=1.5.0 but it's been released for over half a year so it should be fine.