-
Notifications
You must be signed in to change notification settings - Fork 85
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
Look into using difftastic for better diffs #57
Comments
Possibly one immediate improvement would be to ignore whitespace changes? Might also need to do something like that for the (new) rev-check @alfsb |
Although it has to do with revchecks, both About whitespaces in diffs, I think this can be an option. The separated diff page may contain, for example, checkboxes for Whitespace is always a PITA, because it is always important. While it is good to be able to observe only textual differences, having a way to observe WS changes has also its value. For example, the |
About specifically ignoring whitespace changes, it would be possible, but with caveats. Some internal whitespaces changes are important (for example, ws inside some tags that breaks automatic linking) and even changes that may or may not be synced in translations (for example) https://github.com/php/doc-en/pull/3837/files But most or inter textual ws changes can be ignored. It's possible, for example, in the case of outdated files, to compare the contents of two versions of an en file, the last and the annotated in revtag, but trimming all lines and blank lines before comparison. If two "trimmed" files compare equals, there are no textual changes, and these files would not be marked outdated. But it will slow, even more so as these cases of "line trim equals" accumulate. Some form of automatic hash bumping will be necessary after a while. |
We're already using Maybe we could also use |
The descriptions of It will ignore ws changing within lines, and that's unfortunate. An option like |
As requested by @Girgias.
https://difftastic.wilfred.me.uk/
The text was updated successfully, but these errors were encountered: