-
-
Notifications
You must be signed in to change notification settings - Fork 427
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
Check filtered finding when error is on another line than git diff
#187
Comments
I encountered a similar problem when using flake8. + import yaml
import os # H306 imports not in alphabetical order
import yaml # F811 redefinition of unused |
Now, you can use
It could be interesting to implement for github-pr-review reporter, but it's too specific issue for github review API, so I don't have an immediate plan to implement it. |
@haya14busa usage of I would like to implement such feature, maybe you have some thoughts on that? I think the |
On second thought, it sounds interesting. @Le6ow5k1 can you implement it? |
@haya14busa yes, I will |
And introduce the command line flag `filter-by-added-lines` to turn off the default behavior. References reviewdog#187
And introduce the command line flag `filter-by-added-lines` to turn off the default behavior. References reviewdog#187
And introduce the command line flag `filter-by-added-lines` to turn off the default behavior. References reviewdog#187
And introduce the command line flag `filter-by-added-lines` to turn off the default behavior. References reviewdog#187
And introduce the command line flag `filter-mode` with options for filtering checks by "added" lines or "diff_context". References reviewdog#187
And introduce the command line flag `filter-mode` with options for filtering checks by "added" lines or "diff_context". References reviewdog#187
And introduce the command line flag `filter-mode` with options for filtering checks by "added" lines or "diff_context". References reviewdog#187
I'm not sure whether my problem relates to this issue or not. So I decided to ask here first, before creating a new issue. I'm using:
For this configuration, I can easily create a PR with a new linter error that reviewdog will miss. Let's say I have a constant that is defined in one file (with all other constants) and used only once in another place. Removing this single usage will lead to See this PR for a real-life example: moira-alert/moira#468 @haya14busa @Le6ow5k1 am I missing something? Is it possible to run reviewdog on the entire codebase, not just diff? Assuming I have zero linter complaints for current master branch. |
@beevee |
@Le6ow5k1 Is there a way to make |
I believe currently there is no way to use As a workaround you might try to specify diff between current and first commit |
Now you can use If you want, you can also use The new binary is not released yet, but I'll release it in a few days. |
The new binary released: https://github.com/reviewdog/reviewdog/blob/master/CHANGELOG.md#v0100---2020-05-07 |
I'm trying out to create a PHP Linter.
I have a file like this:
My php linter gives the following error:
And Reviewdog marks this finding as filtered:
That's because Reviewdog does a strict lookup for the given row number in the git diff. But in PHP the error will sometimes be on the next line.
Any idea how to solve this?
Doesn't Github allow for adding checks to lines that didn't change? It always shows ±5 lines before and after right? Maybe we can take that margin into account here?
The text was updated successfully, but these errors were encountered: