To toggle whether Visual Studio Code should ignore leading/trailing whitespace click this icon:įor more sophisticated whitespace handling, check out the Programming Language Aware Diff section.Comparing two files side by side is an important task for any developer, especially when it comes to identifying differences between versions of the same file. For example, Python uses the indentation of lines to determine which control flow structure the current line belongs to, and Markdown uses two trailing whitespaces to indicate a line break. There are a few notable exceptions though. They don’t have a meaning in most programming languages and would only add visual noise to the diff. To switch between the side-by-side and inline diff mode, simply open the action menu and select Inline View: Showing Leading/Trailing Whitespace Changesīy default VS Code ignores added or removed whitespaces at the beginning or end of a line. It may take some time to get used to it, but it significantly reduces the amount of screen space required: This is achieved by first showing all the lines that have been deleted at the current position, followed by all the lines that have been inserted. The inline diff shows the old and new version of the code within the same document. If your code has very long lines or you don’t have a lot of horizontal screen space, you might want to switch to the inline diff mode (called unified diff outside of VS Code). The default diff mode in Visual Studio Code displays the old and new code side-by-side. You may want to check the marketplace page first to see if your languages are included. Please note that not all programming languages are supported yet. Click it to switch to the smart diff mode: After opening any diff (see Open The Diff Viewer) you should find the following icon in the upper right corner.
#COMPARE FILES IN VSCODE INSTALL#
To give it a try, install SemanticDiff from the marketplace. This makes it possible to hide irrelevant changes and to detect moved code: SemanticDiff parses the code of the files and compares their compiler representation instead of their text. To solve this, we have developed a VS Code extension that generates smarter diffs. This can lead to noisy diffs as many programming languages allow you to add optional semicolons or line breaks that show up as changes without having any effect on your program. The diff viewer built into Visual Studio Code compares files line-by-line and highlights every character that has changed. Here are some tips how you can get better diffs. In some cases, however, you can get better results by installing third-party extensions or by fine-tuning some settings. The Visual Studio Code diff viewer provides a good out-of-the-box experience for many programming languages and other text-based file formats.
Below I have collected some tips on how you can further configure and optimize the diff viewer to your needs. This should give you basic understanding of how diffs work in Visual Studio Code. Only the parts of the line that actually differ have an intense color: Lines that exist in both versions but contain differences use a light red and green background. Lines that exist only in the new version are displayed using a diagonal pattern on the left side and bright green background on the right side: Lines that exist only in the old version are displayed using a bright red background on the left side and a diagonal pattern on the right side: The differences between the two files are usually highlighted using the colors red and green, but the colors may vary depending on theme you are using. The right side shows the new file, which is the second file you selected or the new git revision.
On the left side you can see the content of the old file, which is either the first file you selected or the older git revision of the file. Diff Viewer ExplanationĪfter following any of the methods described above, the diff viewer should open. Check out the marketplace page to learn more about them.
The Diff Folders extension offers several other features, such as copying files between the two folders.
0 kommentar(er)
