-
Notifications
You must be signed in to change notification settings - Fork 8
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
Differentiate between new lines and modified lines #31
Comments
What do you mean "omit modified lines from the reported errors"? The purpose of flake8-diff is to output errors only for the modified lines. Are you trying to do something else? |
I'd like an option to only report errors in chunks of lines that are added ; i.e. the vcs diff program is not able to match the lines with lines in the pre-existing code. |
can you give an example? |
I'd like it to skip checking modified line in the following, and report errors in the two new lines. -old line
+modified line
+new line 1
+new line 2 |
This can be customized for git in https://github.com/dealertrack/flake8-diff/blob/master/flake8diff/vcs/git.py#L67 although not sure what the parameter should be. Also not sure how it would be implemented for other backends like |
The If I was implementing this, I would not be looking at modify Instead I would be modifying |
sounds reasonable to me. just to clarify - you would like to ignore modified lines however Im not sure how would that work on a file where both lines are added and modified. either way you are more then welcome to try to implement this. having some concrete example might help with figuring out all the edge cases |
When working on a codebase which has violations which are baked in, such as CamelCase method names, modifications of those lines are not new violations, and 'fixing' them would create new bugs part of any release other than a major release.
It would be nice if there was an option to omit modified lines from the reported errors.
The text was updated successfully, but these errors were encountered: