pingasil.blogg.se - Diffmerge ignore whitespace

#Diffmerge ignore whitespace how to#
#Diffmerge ignore whitespace update#
#Diffmerge ignore whitespace code#

Just a ping on this, and an example of formatting changes we’d like to beĪble turn off and not show in the diff editor (like -w for git diff as

Is this something we could swarm on and get done in a pull request? Other tool for visual diff that does ignore white space ? On Wed, at 4:10 PM Shawn Mannen there seems to be no feedback for VS code, can someone suggest I need this to work when a file is clicked in the source control tab which Is there a document that includes setup steps?

#Diffmerge ignore whitespace how to#

(Is there a way to escalate issues to a Microsoft product team, so it doesn’t have to wait for an open source volunteer to fix it?)ĭoes anyone know how to integrate beyond compare into vscode that would Thanks for keeping this issue open please consider it very valuable.

That led to me using it as my main editor.) The way I learned about VSCode in the first place was I was searching for a more readable diff tool and someone recommended it. I previously had an editor that I liked, except the diff was inadequate. (Review quality is safety critical in some fields (like control systems) and good diffs are a tremendous help.

I think the diff in VSCode has been great except for this one very strange shortcoming. Surely we don’t want people to have to leave the smooth flow of using VSCode to view everyday diffs with some other tool? I’m sure a lot more people are getting burned by this (and making policy changes to work around it) than just the few who bother to comment here. Then I have to go on a research quest to find extensions to fix the problem, and create a new policy for everyone that auto-formatter now must be run at checkpoint times to minimize the risk of unreadable diffs.

#Diffmerge ignore whitespace code#

Until, someone on the team used an auto-formatter (which should be no problem), but suddenly I can’t review the real code changes among the hundreds of places where something like (1,2) got changed to (1, 2) and I have to spend an hour searching for the obvious expected “ignore ALL whitespace” setting… then realize it actually doesn’t exist. I’ve loved the convenience of having instant diffs in VSCode. You are receiving this because you are subscribed to this thread.MessageĮnterprisewide Programmer Analyst, Principal Triage notifications on the go with GitHub Mobile for iOS Reply to this email directly, view it on GitHub On Mon, at 8:57 PM Shuai Zhang to be already solved. Of the ‘a’ in the top line, even though, the lines are functionally the In the above example the diff editor will flag the difference on both sides But, It does Not ignore ALL whitespace changes.

#Diffmerge ignore whitespace update#

This update will ignore leading and trailing This is why I support this feature request.Īs an industry could stand to move away from having opinions about how other developers format their source code, in favor of expressiveness, ease and inclusiveness. Each developer can then individually format code according to how each thinks best. Do not impose whitespace and indentation formatting constraints for source code if the language itself does not.

Moreover, this raises the bar for entry for new people, making coding a less inclusive industryĭo away with whitespace as a concern when writing or reviewing code.

Opinionated formatters impose a cognitive load on everyone, making individual coders work harder to read their own code

Expressiveness and facility is important when coding and reading code, and I would argue this is top priority.

This reduces errors and cognitive load when reviewing code and when troubleshooting. The problem that formatters solve: whitespace and indentation is consistent across developers and time, so that changes between commits are obvious. I suspect that opinionated formatters such as Prettier solve one problem but at high cost.

As with everything, I have Thoughts On This.