Make the pre-defined 'errorformat' an input variable #49
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
|
Sorry for the late response. Thanks! |
|
🚀 [bumpr] Bumped! New version:v3.10.0 Changes:v3.9.0...v3.10.0 |
|
Hi, @salzmannsusan! We merged your PR to reviewdog! 🐶 We just invited you to join the @reviewdog organization on GitHub. Thanks again! |
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.
When creating new, custom linter rules with flake8 and ast, the plugin code has to match this regex: ^[A-Z]{1,3}[0-9]{0,3}$.
However, the pre-defined 'errorformat'
flake8does not parse all these plugin codes as expected. But the pre-definedpep8does.To be able to see warnings for custom linter rules, it would be necessary to make the error format an (optional) input parameter. (#48)
This was done here.