From 16bd7cbc91edba340b34a6352fea81e5e9175460 Mon Sep 17 00:00:00 2001 From: Simon Cropp Date: Sat, 1 Aug 2026 09:11:35 +1000 Subject: [PATCH] Add opt in newline tolerance settings Restores, as opt in, the two tolerances removed in 7253acb. VerifierSettings.FixNewlinesOnRead normalizes \r\n and \r to \n when reading verified files, instead of rejecting a verified file that contains a carriage return. VerifierSettings.IgnoreTrailingNewline treats a verified file that ends in a single \n, where that newline accounts for the entire difference in length, as equal to the received content. Both are global and guarded by ThrowIfVerifyHasBeenRun, so a module initializer is the only place to set them. That makes either a repo level fix requiring no per developer setup, which is what #1824 asks for. Neither is a replacement for the .gitattributes and EditorConfig settings, and enabling them has side effects: line endings on disk diverge between accept workflows, the misconfiguration is no longer surfaced anywhere, diff output during a real mismatch is noisier, reported content no longer matches the bytes on disk, normalizing allocates, and IgnoreTrailingNewline can mask output that stops emitting a trailing newline. All documented in the new docs/newline-tolerance.md, linked from the exception message, the xml docs, and the doc index. Closes #1824 --- docs/mdsource/doc-index.include.md | 1 + docs/mdsource/newline-tolerance.source.md | 70 +++++++++++++ docs/mdsource/text-file-settings.include.md | 7 +- docs/newline-tolerance.md | 99 +++++++++++++++++++ docs/readme.md | 1 + docs/wiz/Linux_Other_Cli_Expecto_AppVeyor.md | 7 +- .../Linux_Other_Cli_Expecto_AzureDevOps.md | 7 +- .../Linux_Other_Cli_Expecto_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Cli_Expecto_None.md | 7 +- docs/wiz/Linux_Other_Cli_Fixie_AppVeyor.md | 7 +- docs/wiz/Linux_Other_Cli_Fixie_AzureDevOps.md | 7 +- .../Linux_Other_Cli_Fixie_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Cli_Fixie_None.md | 7 +- docs/wiz/Linux_Other_Cli_MSTest_AppVeyor.md | 7 +- .../wiz/Linux_Other_Cli_MSTest_AzureDevOps.md | 7 +- .../Linux_Other_Cli_MSTest_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Cli_MSTest_None.md | 7 +- docs/wiz/Linux_Other_Cli_NUnit_AppVeyor.md | 7 +- docs/wiz/Linux_Other_Cli_NUnit_AzureDevOps.md | 7 +- .../Linux_Other_Cli_NUnit_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Cli_NUnit_None.md | 7 +- docs/wiz/Linux_Other_Cli_TUnit_AppVeyor.md | 7 +- docs/wiz/Linux_Other_Cli_TUnit_AzureDevOps.md | 7 +- .../Linux_Other_Cli_TUnit_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Cli_TUnit_None.md | 7 +- docs/wiz/Linux_Other_Cli_XunitV3_AppVeyor.md | 7 +- .../Linux_Other_Cli_XunitV3_AzureDevOps.md | 7 +- .../Linux_Other_Cli_XunitV3_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Cli_XunitV3_None.md | 7 +- docs/wiz/Linux_Other_Gui_Expecto_AppVeyor.md | 7 +- .../Linux_Other_Gui_Expecto_AzureDevOps.md | 7 +- .../Linux_Other_Gui_Expecto_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Gui_Expecto_None.md | 7 +- docs/wiz/Linux_Other_Gui_Fixie_AppVeyor.md | 7 +- docs/wiz/Linux_Other_Gui_Fixie_AzureDevOps.md | 7 +- .../Linux_Other_Gui_Fixie_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Gui_Fixie_None.md | 7 +- docs/wiz/Linux_Other_Gui_MSTest_AppVeyor.md | 7 +- .../wiz/Linux_Other_Gui_MSTest_AzureDevOps.md | 7 +- .../Linux_Other_Gui_MSTest_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Gui_MSTest_None.md | 7 +- docs/wiz/Linux_Other_Gui_NUnit_AppVeyor.md | 7 +- docs/wiz/Linux_Other_Gui_NUnit_AzureDevOps.md | 7 +- .../Linux_Other_Gui_NUnit_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Gui_NUnit_None.md | 7 +- docs/wiz/Linux_Other_Gui_TUnit_AppVeyor.md | 7 +- docs/wiz/Linux_Other_Gui_TUnit_AzureDevOps.md | 7 +- .../Linux_Other_Gui_TUnit_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Gui_TUnit_None.md | 7 +- docs/wiz/Linux_Other_Gui_XunitV3_AppVeyor.md | 7 +- .../Linux_Other_Gui_XunitV3_AzureDevOps.md | 7 +- .../Linux_Other_Gui_XunitV3_GitHubActions.md | 7 +- docs/wiz/Linux_Other_Gui_XunitV3_None.md | 7 +- docs/wiz/Linux_Rider_Cli_Expecto_AppVeyor.md | 7 +- .../Linux_Rider_Cli_Expecto_AzureDevOps.md | 7 +- .../Linux_Rider_Cli_Expecto_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Cli_Expecto_None.md | 7 +- docs/wiz/Linux_Rider_Cli_Fixie_AppVeyor.md | 7 +- docs/wiz/Linux_Rider_Cli_Fixie_AzureDevOps.md | 7 +- .../Linux_Rider_Cli_Fixie_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Cli_Fixie_None.md | 7 +- docs/wiz/Linux_Rider_Cli_MSTest_AppVeyor.md | 7 +- .../wiz/Linux_Rider_Cli_MSTest_AzureDevOps.md | 7 +- .../Linux_Rider_Cli_MSTest_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Cli_MSTest_None.md | 7 +- docs/wiz/Linux_Rider_Cli_NUnit_AppVeyor.md | 7 +- docs/wiz/Linux_Rider_Cli_NUnit_AzureDevOps.md | 7 +- .../Linux_Rider_Cli_NUnit_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Cli_NUnit_None.md | 7 +- docs/wiz/Linux_Rider_Cli_TUnit_AppVeyor.md | 7 +- docs/wiz/Linux_Rider_Cli_TUnit_AzureDevOps.md | 7 +- .../Linux_Rider_Cli_TUnit_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Cli_TUnit_None.md | 7 +- docs/wiz/Linux_Rider_Cli_XunitV3_AppVeyor.md | 7 +- .../Linux_Rider_Cli_XunitV3_AzureDevOps.md | 7 +- .../Linux_Rider_Cli_XunitV3_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Cli_XunitV3_None.md | 7 +- docs/wiz/Linux_Rider_Gui_Expecto_AppVeyor.md | 7 +- .../Linux_Rider_Gui_Expecto_AzureDevOps.md | 7 +- .../Linux_Rider_Gui_Expecto_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Gui_Expecto_None.md | 7 +- docs/wiz/Linux_Rider_Gui_Fixie_AppVeyor.md | 7 +- docs/wiz/Linux_Rider_Gui_Fixie_AzureDevOps.md | 7 +- .../Linux_Rider_Gui_Fixie_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Gui_Fixie_None.md | 7 +- docs/wiz/Linux_Rider_Gui_MSTest_AppVeyor.md | 7 +- .../wiz/Linux_Rider_Gui_MSTest_AzureDevOps.md | 7 +- .../Linux_Rider_Gui_MSTest_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Gui_MSTest_None.md | 7 +- docs/wiz/Linux_Rider_Gui_NUnit_AppVeyor.md | 7 +- docs/wiz/Linux_Rider_Gui_NUnit_AzureDevOps.md | 7 +- .../Linux_Rider_Gui_NUnit_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Gui_NUnit_None.md | 7 +- docs/wiz/Linux_Rider_Gui_TUnit_AppVeyor.md | 7 +- docs/wiz/Linux_Rider_Gui_TUnit_AzureDevOps.md | 7 +- .../Linux_Rider_Gui_TUnit_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Gui_TUnit_None.md | 7 +- docs/wiz/Linux_Rider_Gui_XunitV3_AppVeyor.md | 7 +- .../Linux_Rider_Gui_XunitV3_AzureDevOps.md | 7 +- .../Linux_Rider_Gui_XunitV3_GitHubActions.md | 7 +- docs/wiz/Linux_Rider_Gui_XunitV3_None.md | 7 +- docs/wiz/MacOS_Other_Cli_Expecto_AppVeyor.md | 7 +- .../MacOS_Other_Cli_Expecto_AzureDevOps.md | 7 +- .../MacOS_Other_Cli_Expecto_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Cli_Expecto_None.md | 7 +- docs/wiz/MacOS_Other_Cli_Fixie_AppVeyor.md | 7 +- docs/wiz/MacOS_Other_Cli_Fixie_AzureDevOps.md | 7 +- .../MacOS_Other_Cli_Fixie_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Cli_Fixie_None.md | 7 +- docs/wiz/MacOS_Other_Cli_MSTest_AppVeyor.md | 7 +- .../wiz/MacOS_Other_Cli_MSTest_AzureDevOps.md | 7 +- .../MacOS_Other_Cli_MSTest_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Cli_MSTest_None.md | 7 +- docs/wiz/MacOS_Other_Cli_NUnit_AppVeyor.md | 7 +- docs/wiz/MacOS_Other_Cli_NUnit_AzureDevOps.md | 7 +- .../MacOS_Other_Cli_NUnit_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Cli_NUnit_None.md | 7 +- docs/wiz/MacOS_Other_Cli_TUnit_AppVeyor.md | 7 +- docs/wiz/MacOS_Other_Cli_TUnit_AzureDevOps.md | 7 +- .../MacOS_Other_Cli_TUnit_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Cli_TUnit_None.md | 7 +- docs/wiz/MacOS_Other_Cli_XunitV3_AppVeyor.md | 7 +- .../MacOS_Other_Cli_XunitV3_AzureDevOps.md | 7 +- .../MacOS_Other_Cli_XunitV3_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Cli_XunitV3_None.md | 7 +- docs/wiz/MacOS_Other_Gui_Expecto_AppVeyor.md | 7 +- .../MacOS_Other_Gui_Expecto_AzureDevOps.md | 7 +- .../MacOS_Other_Gui_Expecto_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Gui_Expecto_None.md | 7 +- docs/wiz/MacOS_Other_Gui_Fixie_AppVeyor.md | 7 +- docs/wiz/MacOS_Other_Gui_Fixie_AzureDevOps.md | 7 +- .../MacOS_Other_Gui_Fixie_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Gui_Fixie_None.md | 7 +- docs/wiz/MacOS_Other_Gui_MSTest_AppVeyor.md | 7 +- .../wiz/MacOS_Other_Gui_MSTest_AzureDevOps.md | 7 +- .../MacOS_Other_Gui_MSTest_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Gui_MSTest_None.md | 7 +- docs/wiz/MacOS_Other_Gui_NUnit_AppVeyor.md | 7 +- docs/wiz/MacOS_Other_Gui_NUnit_AzureDevOps.md | 7 +- .../MacOS_Other_Gui_NUnit_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Gui_NUnit_None.md | 7 +- docs/wiz/MacOS_Other_Gui_TUnit_AppVeyor.md | 7 +- docs/wiz/MacOS_Other_Gui_TUnit_AzureDevOps.md | 7 +- .../MacOS_Other_Gui_TUnit_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Gui_TUnit_None.md | 7 +- docs/wiz/MacOS_Other_Gui_XunitV3_AppVeyor.md | 7 +- .../MacOS_Other_Gui_XunitV3_AzureDevOps.md | 7 +- .../MacOS_Other_Gui_XunitV3_GitHubActions.md | 7 +- docs/wiz/MacOS_Other_Gui_XunitV3_None.md | 7 +- docs/wiz/MacOS_Rider_Cli_Expecto_AppVeyor.md | 7 +- .../MacOS_Rider_Cli_Expecto_AzureDevOps.md | 7 +- .../MacOS_Rider_Cli_Expecto_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Cli_Expecto_None.md | 7 +- docs/wiz/MacOS_Rider_Cli_Fixie_AppVeyor.md | 7 +- docs/wiz/MacOS_Rider_Cli_Fixie_AzureDevOps.md | 7 +- .../MacOS_Rider_Cli_Fixie_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Cli_Fixie_None.md | 7 +- docs/wiz/MacOS_Rider_Cli_MSTest_AppVeyor.md | 7 +- .../wiz/MacOS_Rider_Cli_MSTest_AzureDevOps.md | 7 +- .../MacOS_Rider_Cli_MSTest_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Cli_MSTest_None.md | 7 +- docs/wiz/MacOS_Rider_Cli_NUnit_AppVeyor.md | 7 +- docs/wiz/MacOS_Rider_Cli_NUnit_AzureDevOps.md | 7 +- .../MacOS_Rider_Cli_NUnit_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Cli_NUnit_None.md | 7 +- docs/wiz/MacOS_Rider_Cli_TUnit_AppVeyor.md | 7 +- docs/wiz/MacOS_Rider_Cli_TUnit_AzureDevOps.md | 7 +- .../MacOS_Rider_Cli_TUnit_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Cli_TUnit_None.md | 7 +- docs/wiz/MacOS_Rider_Cli_XunitV3_AppVeyor.md | 7 +- .../MacOS_Rider_Cli_XunitV3_AzureDevOps.md | 7 +- .../MacOS_Rider_Cli_XunitV3_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Cli_XunitV3_None.md | 7 +- docs/wiz/MacOS_Rider_Gui_Expecto_AppVeyor.md | 7 +- .../MacOS_Rider_Gui_Expecto_AzureDevOps.md | 7 +- .../MacOS_Rider_Gui_Expecto_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Gui_Expecto_None.md | 7 +- docs/wiz/MacOS_Rider_Gui_Fixie_AppVeyor.md | 7 +- docs/wiz/MacOS_Rider_Gui_Fixie_AzureDevOps.md | 7 +- .../MacOS_Rider_Gui_Fixie_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Gui_Fixie_None.md | 7 +- docs/wiz/MacOS_Rider_Gui_MSTest_AppVeyor.md | 7 +- .../wiz/MacOS_Rider_Gui_MSTest_AzureDevOps.md | 7 +- .../MacOS_Rider_Gui_MSTest_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Gui_MSTest_None.md | 7 +- docs/wiz/MacOS_Rider_Gui_NUnit_AppVeyor.md | 7 +- docs/wiz/MacOS_Rider_Gui_NUnit_AzureDevOps.md | 7 +- .../MacOS_Rider_Gui_NUnit_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Gui_NUnit_None.md | 7 +- docs/wiz/MacOS_Rider_Gui_TUnit_AppVeyor.md | 7 +- docs/wiz/MacOS_Rider_Gui_TUnit_AzureDevOps.md | 7 +- .../MacOS_Rider_Gui_TUnit_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Gui_TUnit_None.md | 7 +- docs/wiz/MacOS_Rider_Gui_XunitV3_AppVeyor.md | 7 +- .../MacOS_Rider_Gui_XunitV3_AzureDevOps.md | 7 +- .../MacOS_Rider_Gui_XunitV3_GitHubActions.md | 7 +- docs/wiz/MacOS_Rider_Gui_XunitV3_None.md | 7 +- .../wiz/Windows_Other_Cli_Expecto_AppVeyor.md | 7 +- .../Windows_Other_Cli_Expecto_AzureDevOps.md | 7 +- ...Windows_Other_Cli_Expecto_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Cli_Expecto_None.md | 7 +- docs/wiz/Windows_Other_Cli_Fixie_AppVeyor.md | 7 +- .../Windows_Other_Cli_Fixie_AzureDevOps.md | 7 +- .../Windows_Other_Cli_Fixie_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Cli_Fixie_None.md | 7 +- docs/wiz/Windows_Other_Cli_MSTest_AppVeyor.md | 7 +- .../Windows_Other_Cli_MSTest_AzureDevOps.md | 7 +- .../Windows_Other_Cli_MSTest_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Cli_MSTest_None.md | 7 +- docs/wiz/Windows_Other_Cli_NUnit_AppVeyor.md | 7 +- .../Windows_Other_Cli_NUnit_AzureDevOps.md | 7 +- .../Windows_Other_Cli_NUnit_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Cli_NUnit_None.md | 7 +- docs/wiz/Windows_Other_Cli_TUnit_AppVeyor.md | 7 +- .../Windows_Other_Cli_TUnit_AzureDevOps.md | 7 +- .../Windows_Other_Cli_TUnit_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Cli_TUnit_None.md | 7 +- .../wiz/Windows_Other_Cli_XunitV3_AppVeyor.md | 7 +- .../Windows_Other_Cli_XunitV3_AzureDevOps.md | 7 +- ...Windows_Other_Cli_XunitV3_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Cli_XunitV3_None.md | 7 +- .../wiz/Windows_Other_Gui_Expecto_AppVeyor.md | 7 +- .../Windows_Other_Gui_Expecto_AzureDevOps.md | 7 +- ...Windows_Other_Gui_Expecto_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Gui_Expecto_None.md | 7 +- docs/wiz/Windows_Other_Gui_Fixie_AppVeyor.md | 7 +- .../Windows_Other_Gui_Fixie_AzureDevOps.md | 7 +- .../Windows_Other_Gui_Fixie_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Gui_Fixie_None.md | 7 +- docs/wiz/Windows_Other_Gui_MSTest_AppVeyor.md | 7 +- .../Windows_Other_Gui_MSTest_AzureDevOps.md | 7 +- .../Windows_Other_Gui_MSTest_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Gui_MSTest_None.md | 7 +- docs/wiz/Windows_Other_Gui_NUnit_AppVeyor.md | 7 +- .../Windows_Other_Gui_NUnit_AzureDevOps.md | 7 +- .../Windows_Other_Gui_NUnit_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Gui_NUnit_None.md | 7 +- docs/wiz/Windows_Other_Gui_TUnit_AppVeyor.md | 7 +- .../Windows_Other_Gui_TUnit_AzureDevOps.md | 7 +- .../Windows_Other_Gui_TUnit_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Gui_TUnit_None.md | 7 +- .../wiz/Windows_Other_Gui_XunitV3_AppVeyor.md | 7 +- .../Windows_Other_Gui_XunitV3_AzureDevOps.md | 7 +- ...Windows_Other_Gui_XunitV3_GitHubActions.md | 7 +- docs/wiz/Windows_Other_Gui_XunitV3_None.md | 7 +- .../wiz/Windows_Rider_Cli_Expecto_AppVeyor.md | 7 +- .../Windows_Rider_Cli_Expecto_AzureDevOps.md | 7 +- ...Windows_Rider_Cli_Expecto_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Cli_Expecto_None.md | 7 +- docs/wiz/Windows_Rider_Cli_Fixie_AppVeyor.md | 7 +- .../Windows_Rider_Cli_Fixie_AzureDevOps.md | 7 +- .../Windows_Rider_Cli_Fixie_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Cli_Fixie_None.md | 7 +- docs/wiz/Windows_Rider_Cli_MSTest_AppVeyor.md | 7 +- .../Windows_Rider_Cli_MSTest_AzureDevOps.md | 7 +- .../Windows_Rider_Cli_MSTest_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Cli_MSTest_None.md | 7 +- docs/wiz/Windows_Rider_Cli_NUnit_AppVeyor.md | 7 +- .../Windows_Rider_Cli_NUnit_AzureDevOps.md | 7 +- .../Windows_Rider_Cli_NUnit_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Cli_NUnit_None.md | 7 +- docs/wiz/Windows_Rider_Cli_TUnit_AppVeyor.md | 7 +- .../Windows_Rider_Cli_TUnit_AzureDevOps.md | 7 +- .../Windows_Rider_Cli_TUnit_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Cli_TUnit_None.md | 7 +- .../wiz/Windows_Rider_Cli_XunitV3_AppVeyor.md | 7 +- .../Windows_Rider_Cli_XunitV3_AzureDevOps.md | 7 +- ...Windows_Rider_Cli_XunitV3_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Cli_XunitV3_None.md | 7 +- .../wiz/Windows_Rider_Gui_Expecto_AppVeyor.md | 7 +- .../Windows_Rider_Gui_Expecto_AzureDevOps.md | 7 +- ...Windows_Rider_Gui_Expecto_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Gui_Expecto_None.md | 7 +- docs/wiz/Windows_Rider_Gui_Fixie_AppVeyor.md | 7 +- .../Windows_Rider_Gui_Fixie_AzureDevOps.md | 7 +- .../Windows_Rider_Gui_Fixie_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Gui_Fixie_None.md | 7 +- docs/wiz/Windows_Rider_Gui_MSTest_AppVeyor.md | 7 +- .../Windows_Rider_Gui_MSTest_AzureDevOps.md | 7 +- .../Windows_Rider_Gui_MSTest_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Gui_MSTest_None.md | 7 +- docs/wiz/Windows_Rider_Gui_NUnit_AppVeyor.md | 7 +- .../Windows_Rider_Gui_NUnit_AzureDevOps.md | 7 +- .../Windows_Rider_Gui_NUnit_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Gui_NUnit_None.md | 7 +- docs/wiz/Windows_Rider_Gui_TUnit_AppVeyor.md | 7 +- .../Windows_Rider_Gui_TUnit_AzureDevOps.md | 7 +- .../Windows_Rider_Gui_TUnit_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Gui_TUnit_None.md | 7 +- .../wiz/Windows_Rider_Gui_XunitV3_AppVeyor.md | 7 +- .../Windows_Rider_Gui_XunitV3_AzureDevOps.md | 7 +- ...Windows_Rider_Gui_XunitV3_GitHubActions.md | 7 +- docs/wiz/Windows_Rider_Gui_XunitV3_None.md | 7 +- ...tudioWithReSharper_Cli_Expecto_AppVeyor.md | 7 +- ...ioWithReSharper_Cli_Expecto_AzureDevOps.md | 7 +- ...WithReSharper_Cli_Expecto_GitHubActions.md | 7 +- ...ualStudioWithReSharper_Cli_Expecto_None.md | 7 +- ...lStudioWithReSharper_Cli_Fixie_AppVeyor.md | 7 +- ...udioWithReSharper_Cli_Fixie_AzureDevOps.md | 7 +- ...ioWithReSharper_Cli_Fixie_GitHubActions.md | 7 +- ...isualStudioWithReSharper_Cli_Fixie_None.md | 7 +- ...StudioWithReSharper_Cli_MSTest_AppVeyor.md | 7 +- ...dioWithReSharper_Cli_MSTest_AzureDevOps.md | 7 +- ...oWithReSharper_Cli_MSTest_GitHubActions.md | 7 +- ...sualStudioWithReSharper_Cli_MSTest_None.md | 7 +- ...lStudioWithReSharper_Cli_NUnit_AppVeyor.md | 7 +- ...udioWithReSharper_Cli_NUnit_AzureDevOps.md | 7 +- ...ioWithReSharper_Cli_NUnit_GitHubActions.md | 7 +- ...isualStudioWithReSharper_Cli_NUnit_None.md | 7 +- ...lStudioWithReSharper_Cli_TUnit_AppVeyor.md | 7 +- ...udioWithReSharper_Cli_TUnit_AzureDevOps.md | 7 +- ...ioWithReSharper_Cli_TUnit_GitHubActions.md | 7 +- ...isualStudioWithReSharper_Cli_TUnit_None.md | 7 +- ...tudioWithReSharper_Cli_XunitV3_AppVeyor.md | 7 +- ...ioWithReSharper_Cli_XunitV3_AzureDevOps.md | 7 +- ...WithReSharper_Cli_XunitV3_GitHubActions.md | 7 +- ...ualStudioWithReSharper_Cli_XunitV3_None.md | 7 +- ...tudioWithReSharper_Gui_Expecto_AppVeyor.md | 7 +- ...ioWithReSharper_Gui_Expecto_AzureDevOps.md | 7 +- ...WithReSharper_Gui_Expecto_GitHubActions.md | 7 +- ...ualStudioWithReSharper_Gui_Expecto_None.md | 7 +- ...lStudioWithReSharper_Gui_Fixie_AppVeyor.md | 7 +- ...udioWithReSharper_Gui_Fixie_AzureDevOps.md | 7 +- ...ioWithReSharper_Gui_Fixie_GitHubActions.md | 7 +- ...isualStudioWithReSharper_Gui_Fixie_None.md | 7 +- ...StudioWithReSharper_Gui_MSTest_AppVeyor.md | 7 +- ...dioWithReSharper_Gui_MSTest_AzureDevOps.md | 7 +- ...oWithReSharper_Gui_MSTest_GitHubActions.md | 7 +- ...sualStudioWithReSharper_Gui_MSTest_None.md | 7 +- ...lStudioWithReSharper_Gui_NUnit_AppVeyor.md | 7 +- ...udioWithReSharper_Gui_NUnit_AzureDevOps.md | 7 +- ...ioWithReSharper_Gui_NUnit_GitHubActions.md | 7 +- ...isualStudioWithReSharper_Gui_NUnit_None.md | 7 +- ...lStudioWithReSharper_Gui_TUnit_AppVeyor.md | 7 +- ...udioWithReSharper_Gui_TUnit_AzureDevOps.md | 7 +- ...ioWithReSharper_Gui_TUnit_GitHubActions.md | 7 +- ...isualStudioWithReSharper_Gui_TUnit_None.md | 7 +- ...tudioWithReSharper_Gui_XunitV3_AppVeyor.md | 7 +- ...ioWithReSharper_Gui_XunitV3_AzureDevOps.md | 7 +- ...WithReSharper_Gui_XunitV3_GitHubActions.md | 7 +- ...ualStudioWithReSharper_Gui_XunitV3_None.md | 7 +- ...ndows_VisualStudio_Cli_Expecto_AppVeyor.md | 7 +- ...ws_VisualStudio_Cli_Expecto_AzureDevOps.md | 7 +- ..._VisualStudio_Cli_Expecto_GitHubActions.md | 7 +- .../Windows_VisualStudio_Cli_Expecto_None.md | 7 +- ...Windows_VisualStudio_Cli_Fixie_AppVeyor.md | 7 +- ...dows_VisualStudio_Cli_Fixie_AzureDevOps.md | 7 +- ...ws_VisualStudio_Cli_Fixie_GitHubActions.md | 7 +- .../Windows_VisualStudio_Cli_Fixie_None.md | 7 +- ...indows_VisualStudio_Cli_MSTest_AppVeyor.md | 7 +- ...ows_VisualStudio_Cli_MSTest_AzureDevOps.md | 7 +- ...s_VisualStudio_Cli_MSTest_GitHubActions.md | 7 +- .../Windows_VisualStudio_Cli_MSTest_None.md | 7 +- ...Windows_VisualStudio_Cli_NUnit_AppVeyor.md | 7 +- ...dows_VisualStudio_Cli_NUnit_AzureDevOps.md | 7 +- ...ws_VisualStudio_Cli_NUnit_GitHubActions.md | 7 +- .../Windows_VisualStudio_Cli_NUnit_None.md | 7 +- ...Windows_VisualStudio_Cli_TUnit_AppVeyor.md | 7 +- ...dows_VisualStudio_Cli_TUnit_AzureDevOps.md | 7 +- ...ws_VisualStudio_Cli_TUnit_GitHubActions.md | 7 +- .../Windows_VisualStudio_Cli_TUnit_None.md | 7 +- ...ndows_VisualStudio_Cli_XunitV3_AppVeyor.md | 7 +- ...ws_VisualStudio_Cli_XunitV3_AzureDevOps.md | 7 +- ..._VisualStudio_Cli_XunitV3_GitHubActions.md | 7 +- .../Windows_VisualStudio_Cli_XunitV3_None.md | 7 +- ...ndows_VisualStudio_Gui_Expecto_AppVeyor.md | 7 +- ...ws_VisualStudio_Gui_Expecto_AzureDevOps.md | 7 +- ..._VisualStudio_Gui_Expecto_GitHubActions.md | 7 +- .../Windows_VisualStudio_Gui_Expecto_None.md | 7 +- ...Windows_VisualStudio_Gui_Fixie_AppVeyor.md | 7 +- ...dows_VisualStudio_Gui_Fixie_AzureDevOps.md | 7 +- ...ws_VisualStudio_Gui_Fixie_GitHubActions.md | 7 +- .../Windows_VisualStudio_Gui_Fixie_None.md | 7 +- ...indows_VisualStudio_Gui_MSTest_AppVeyor.md | 7 +- ...ows_VisualStudio_Gui_MSTest_AzureDevOps.md | 7 +- ...s_VisualStudio_Gui_MSTest_GitHubActions.md | 7 +- .../Windows_VisualStudio_Gui_MSTest_None.md | 7 +- ...Windows_VisualStudio_Gui_NUnit_AppVeyor.md | 7 +- ...dows_VisualStudio_Gui_NUnit_AzureDevOps.md | 7 +- ...ws_VisualStudio_Gui_NUnit_GitHubActions.md | 7 +- .../Windows_VisualStudio_Gui_NUnit_None.md | 7 +- ...Windows_VisualStudio_Gui_TUnit_AppVeyor.md | 7 +- ...dows_VisualStudio_Gui_TUnit_AzureDevOps.md | 7 +- ...ws_VisualStudio_Gui_TUnit_GitHubActions.md | 7 +- .../Windows_VisualStudio_Gui_TUnit_None.md | 7 +- ...ndows_VisualStudio_Gui_XunitV3_AppVeyor.md | 7 +- ...ws_VisualStudio_Gui_XunitV3_AzureDevOps.md | 7 +- ..._VisualStudio_Gui_XunitV3_GitHubActions.md | 7 +- .../Windows_VisualStudio_Gui_XunitV3_None.md | 7 +- readme.md | 8 +- src/ModuleInitDocs/FixNewlinesOnRead.cs | 13 +++ src/ModuleInitDocs/IgnoreTrailingNewline.cs | 13 +++ .../FixNewlinesOnReadTests.cs | 84 ++++++++++++++++ .../IgnoreTrailingNewlineTests.cs | 99 +++++++++++++++++++ src/Verify/Compare/Comparer.cs | 26 ++++- .../Compare/VerifiedLineEndingException.cs | 3 + src/Verify/Serialization/VerifierSettings.cs | 2 + src/Verify/VerifierSettings.cs | 27 +++++ 398 files changed, 2750 insertions(+), 391 deletions(-) create mode 100644 docs/mdsource/newline-tolerance.source.md create mode 100644 docs/newline-tolerance.md create mode 100644 src/ModuleInitDocs/FixNewlinesOnRead.cs create mode 100644 src/ModuleInitDocs/IgnoreTrailingNewline.cs create mode 100644 src/StaticSettingsTests/FixNewlinesOnReadTests.cs create mode 100644 src/StaticSettingsTests/IgnoreTrailingNewlineTests.cs diff --git a/docs/mdsource/doc-index.include.md b/docs/mdsource/doc-index.include.md index c006baaf5c..41747fd3f0 100644 --- a/docs/mdsource/doc-index.include.md +++ b/docs/mdsource/doc-index.include.md @@ -35,6 +35,7 @@ * [Custom Diff Tool](https://github.com/VerifyTests/DiffEngine/blob/master/docs/diff-tool.custom.md) * [Using anonymous types](/docs/anonymous-types.md) * [Verifying binary data](/docs/binary.md) + * [Newline tolerance](/docs/newline-tolerance.md) * [Exception Message Format](/docs/exception-message-format.md) * [Build server](/docs/build-server.md) * [Kill process locking file](/docs/kill-process-locking-file.md) diff --git a/docs/mdsource/newline-tolerance.source.md b/docs/mdsource/newline-tolerance.source.md new file mode 100644 index 0000000000..2b968ead80 --- /dev/null +++ b/docs/mdsource/newline-tolerance.source.md @@ -0,0 +1,70 @@ +## Newline tolerance + +Text snapshots use line-feed newlines, and have no trailing newline. See [Text file settings](/readme.md#text-file-settings) for the source control and editor configuration that keeps them that way. + +The received side of a comparison always conforms, since Verify normalizes content to `\n` before comparing and writes the file itself. The verified side is whatever last wrote it, which is not always Verify. An editor saving with crlf, or a git checkout applying `core.autocrlf=true`, leaves carriage returns in a verified file, and a verified file containing a `\r` is rejected. An editor adding a final newline on save leaves the file one character longer than the content the test produces, and that fails as a mismatch. + +Two opt in settings make the comparison tolerant of those two cases. Both are global, and both throw if called after the first verify has run, so a module initializer is the only place to set them. + +**Neither setting is a replacement for the source control and editor settings.** Those keep the content on disk consistent for everyone working on a repository. The settings below only stop a local misconfiguration from failing the test run, and doing that has [side effects](#side-effects). + + +### FixNewlinesOnRead + +snippet: FixNewlinesOnRead + +With this enabled, `\r\n` and `\r` in a verified file are treated as `\n` when comparing, so a verified file saved with crlf still matches. Normalizing happens in memory only. The file on disk is left as is until it is next written, at which point it is written with lf. + + +### IgnoreTrailingNewline + +snippet: IgnoreTrailingNewline + +With this enabled, a verified file that ends in a single `\n`, where that newline accounts for the entire difference in length, matches the received content. + +The tolerance is deliberately narrow. Two trailing newlines, or any other change in content, still fails. Received files are not covered, since those are written by Verify rather than by an editor. As above, trimming happens in memory only. + + +### Side effects + + +#### Line endings on disk diverge between developers + +Accepting a snapshot through DiffEngineTray, or through the Rider or ReSharper plugins, moves the received file over the verified file. Received files are written by Verify, so the result is lf. Accepting by editing the verified file in a diff editor writes whatever that editor is configured to write, which on Windows is often crlf. With tolerance enabled both accepts pass, so the line endings of a snapshot file end up reflecting the workflow of whoever last accepted it rather than a single convention. + +Whether that flip is visible in a pending git diff depends on the repository. Where `.gitattributes` or `core.autocrlf` normalizes on commit, the crlf stays in the working tree and never reaches a blob. Where it does not, each flip is committed as a change to every line of the file. A one line snapshot change then arrives for review as a whole file diff, and `git blame` attributes every line to the flip rather than to the change that matters. + + +#### IgnoreTrailingNewline can mask a lost trailing newline + +The two settings do not carry the same risk. + +Newline style is already normalized, on both sides. Content is converted to `\n` before it is compared or written, so a `\r` can never reach the received side, and a `\r` in a verified file is always an artifact of tooling rather than something a test produced. Treating it as `\n` cannot hide a change in behavior, since that difference cannot be asserted in the first place. + +A trailing newline is not style, it is content. `a` and `a\n` differ under any newline convention, and are compared exactly. + +The masking that results is narrow, and applies in one direction only. The tolerance fires when the verified file is the longer of the two, so output that starts emitting a trailing newline still fails. Output that stops emitting one, where the verified file has it, now passes. That needs a snapshot whose content genuinely ends in a newline, which serialized objects do not, but verified files and generated text can. + + +#### The misconfiguration is no longer surfaced + +Rejecting a carriage return is the signal that a checkout, an editor, or a build agent working directory is misconfigured. With tolerance enabled the tests pass everywhere, including on CI, so nothing reports the problem. + +Nor does it correct itself. A verified file is only rewritten when a snapshot changes, so a file that has crlf keeps it until something else happens to that snapshot. + + +#### Diff output during a real mismatch + +When a comparison genuinely fails, the received file is written with lf while the verified file keeps its crlf. A diff tool that treats line endings as significant then presents every line as changed, which buries the difference the test is reporting. + + +#### Reported content is not the content on disk + +Normalizing and trimming happen in memory. The verified text passed to a [custom comparer](/docs/comparer.md), to `OnVerifyMismatch`, and into the `FileContent` section of the [exception message](/docs/exception-message-format.md) is the normalized text, not the bytes in the file. Tooling that consumes those and compares against the file on disk sees a difference. + + +#### Performance + +For `FixNewlinesOnRead`, the scan for `\r` runs either way, since it is the same check that drives the rejection. Where a `\r` is found, normalizing allocates and copies the verified content twice, once per replacement. That cost is proportional to snapshot size and is paid for every affected file on every run. On a checkout where every verified file has crlf, that is the entire snapshot corpus copied twice per test run. + +For `IgnoreTrailingNewline`, the added length and character check on every text comparison is not measurable. The trim allocates one copy of the verified content, and only in the case being tolerated. diff --git a/docs/mdsource/text-file-settings.include.md b/docs/mdsource/text-file-settings.include.md index a685ab11a2..d96cbef610 100644 --- a/docs/mdsource/text-file-settings.include.md +++ b/docs/mdsource/text-file-settings.include.md @@ -79,4 +79,9 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. \ No newline at end of file +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). \ No newline at end of file diff --git a/docs/newline-tolerance.md b/docs/newline-tolerance.md new file mode 100644 index 0000000000..8aac7a5dd3 --- /dev/null +++ b/docs/newline-tolerance.md @@ -0,0 +1,99 @@ + + +## Newline tolerance + +Text snapshots use line-feed newlines, and have no trailing newline. See [Text file settings](/readme.md#text-file-settings) for the source control and editor configuration that keeps them that way. + +The received side of a comparison always conforms, since Verify normalizes content to `\n` before comparing and writes the file itself. The verified side is whatever last wrote it, which is not always Verify. An editor saving with crlf, or a git checkout applying `core.autocrlf=true`, leaves carriage returns in a verified file, and a verified file containing a `\r` is rejected. An editor adding a final newline on save leaves the file one character longer than the content the test produces, and that fails as a mismatch. + +Two opt in settings make the comparison tolerant of those two cases. Both are global, and both throw if called after the first verify has run, so a module initializer is the only place to set them. + +**Neither setting is a replacement for the source control and editor settings.** Those keep the content on disk consistent for everyone working on a repository. The settings below only stop a local misconfiguration from failing the test run, and doing that has [side effects](#side-effects). + + +### FixNewlinesOnRead + + + +```cs +public static class ModuleInitializer +{ + [ModuleInitializer] + public static void Init() => + VerifierSettings.FixNewlinesOnRead(); +} +``` +snippet source | anchor + + +With this enabled, `\r\n` and `\r` in a verified file are treated as `\n` when comparing, so a verified file saved with crlf still matches. Normalizing happens in memory only. The file on disk is left as is until it is next written, at which point it is written with lf. + + +### IgnoreTrailingNewline + + + +```cs +public static class ModuleInitializer +{ + [ModuleInitializer] + public static void Init() => + VerifierSettings.IgnoreTrailingNewline(); +} +``` +snippet source | anchor + + +With this enabled, a verified file that ends in a single `\n`, where that newline accounts for the entire difference in length, matches the received content. + +The tolerance is deliberately narrow. Two trailing newlines, or any other change in content, still fails. Received files are not covered, since those are written by Verify rather than by an editor. As above, trimming happens in memory only. + + +### Side effects + + +#### Line endings on disk diverge between developers + +Accepting a snapshot through DiffEngineTray, or through the Rider or ReSharper plugins, moves the received file over the verified file. Received files are written by Verify, so the result is lf. Accepting by editing the verified file in a diff editor writes whatever that editor is configured to write, which on Windows is often crlf. With tolerance enabled both accepts pass, so the line endings of a snapshot file end up reflecting the workflow of whoever last accepted it rather than a single convention. + +Whether that flip is visible in a pending git diff depends on the repository. Where `.gitattributes` or `core.autocrlf` normalizes on commit, the crlf stays in the working tree and never reaches a blob. Where it does not, each flip is committed as a change to every line of the file. A one line snapshot change then arrives for review as a whole file diff, and `git blame` attributes every line to the flip rather than to the change that matters. + + +#### IgnoreTrailingNewline can mask a lost trailing newline + +The two settings do not carry the same risk. + +Newline style is already normalized, on both sides. Content is converted to `\n` before it is compared or written, so a `\r` can never reach the received side, and a `\r` in a verified file is always an artifact of tooling rather than something a test produced. Treating it as `\n` cannot hide a change in behavior, since that difference cannot be asserted in the first place. + +A trailing newline is not style, it is content. `a` and `a\n` differ under any newline convention, and are compared exactly. + +The masking that results is narrow, and applies in one direction only. The tolerance fires when the verified file is the longer of the two, so output that starts emitting a trailing newline still fails. Output that stops emitting one, where the verified file has it, now passes. That needs a snapshot whose content genuinely ends in a newline, which serialized objects do not, but verified files and generated text can. + + +#### The misconfiguration is no longer surfaced + +Rejecting a carriage return is the signal that a checkout, an editor, or a build agent working directory is misconfigured. With tolerance enabled the tests pass everywhere, including on CI, so nothing reports the problem. + +Nor does it correct itself. A verified file is only rewritten when a snapshot changes, so a file that has crlf keeps it until something else happens to that snapshot. + + +#### Diff output during a real mismatch + +When a comparison genuinely fails, the received file is written with lf while the verified file keeps its crlf. A diff tool that treats line endings as significant then presents every line as changed, which buries the difference the test is reporting. + + +#### Reported content is not the content on disk + +Normalizing and trimming happen in memory. The verified text passed to a [custom comparer](/docs/comparer.md), to `OnVerifyMismatch`, and into the `FileContent` section of the [exception message](/docs/exception-message-format.md) is the normalized text, not the bytes in the file. Tooling that consumes those and compares against the file on disk sees a difference. + + +#### Performance + +For `FixNewlinesOnRead`, the scan for `\r` runs either way, since it is the same check that drives the rejection. Where a `\r` is found, normalizing allocates and copies the verified content twice, once per replacement. That cost is proportional to snapshot size and is paid for every affected file on every run. On a checkout where every verified file has crlf, that is the entire snapshot corpus copied twice per test run. + +For `IgnoreTrailingNewline`, the added length and character check on every text comparison is not measurable. The trim allocates one copy of the verified content, and only in the case being tolerated. diff --git a/docs/readme.md b/docs/readme.md index e03dd6fc0b..a2a7c40e98 100644 --- a/docs/readme.md +++ b/docs/readme.md @@ -44,6 +44,7 @@ To change this file edit the source file and then run MarkdownSnippets. * [Custom Diff Tool](https://github.com/VerifyTests/DiffEngine/blob/master/docs/diff-tool.custom.md) * [Using anonymous types](/docs/anonymous-types.md) * [Verifying binary data](/docs/binary.md) + * [Newline tolerance](/docs/newline-tolerance.md) * [Exception Message Format](/docs/exception-message-format.md) * [Build server](/docs/build-server.md) * [Kill process locking file](/docs/kill-process-locking-file.md) diff --git a/docs/wiz/Linux_Other_Cli_Expecto_AppVeyor.md b/docs/wiz/Linux_Other_Cli_Expecto_AppVeyor.md index b632e4fba8..a484e41f9e 100644 --- a/docs/wiz/Linux_Other_Cli_Expecto_AppVeyor.md +++ b/docs/wiz/Linux_Other_Cli_Expecto_AppVeyor.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_Expecto_AzureDevOps.md b/docs/wiz/Linux_Other_Cli_Expecto_AzureDevOps.md index dc7b428296..e813db9cfa 100644 --- a/docs/wiz/Linux_Other_Cli_Expecto_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Cli_Expecto_AzureDevOps.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_Expecto_GitHubActions.md b/docs/wiz/Linux_Other_Cli_Expecto_GitHubActions.md index 40d60b9217..a037542279 100644 --- a/docs/wiz/Linux_Other_Cli_Expecto_GitHubActions.md +++ b/docs/wiz/Linux_Other_Cli_Expecto_GitHubActions.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_Expecto_None.md b/docs/wiz/Linux_Other_Cli_Expecto_None.md index de49d7abd1..988bb34efe 100644 --- a/docs/wiz/Linux_Other_Cli_Expecto_None.md +++ b/docs/wiz/Linux_Other_Cli_Expecto_None.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_Fixie_AppVeyor.md b/docs/wiz/Linux_Other_Cli_Fixie_AppVeyor.md index 79894c84aa..dd011ddea9 100644 --- a/docs/wiz/Linux_Other_Cli_Fixie_AppVeyor.md +++ b/docs/wiz/Linux_Other_Cli_Fixie_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_Fixie_AzureDevOps.md b/docs/wiz/Linux_Other_Cli_Fixie_AzureDevOps.md index 045cb59e9d..2476d8bc6e 100644 --- a/docs/wiz/Linux_Other_Cli_Fixie_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Cli_Fixie_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_Fixie_GitHubActions.md b/docs/wiz/Linux_Other_Cli_Fixie_GitHubActions.md index 6e19b6f845..4d3ce60765 100644 --- a/docs/wiz/Linux_Other_Cli_Fixie_GitHubActions.md +++ b/docs/wiz/Linux_Other_Cli_Fixie_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_Fixie_None.md b/docs/wiz/Linux_Other_Cli_Fixie_None.md index 7be0c993d8..f54a6e7a4f 100644 --- a/docs/wiz/Linux_Other_Cli_Fixie_None.md +++ b/docs/wiz/Linux_Other_Cli_Fixie_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_MSTest_AppVeyor.md b/docs/wiz/Linux_Other_Cli_MSTest_AppVeyor.md index 184b450c05..13fec171bd 100644 --- a/docs/wiz/Linux_Other_Cli_MSTest_AppVeyor.md +++ b/docs/wiz/Linux_Other_Cli_MSTest_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_MSTest_AzureDevOps.md b/docs/wiz/Linux_Other_Cli_MSTest_AzureDevOps.md index 509c5242e5..923d052046 100644 --- a/docs/wiz/Linux_Other_Cli_MSTest_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Cli_MSTest_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_MSTest_GitHubActions.md b/docs/wiz/Linux_Other_Cli_MSTest_GitHubActions.md index 0d17f88b4c..6e460aeb6d 100644 --- a/docs/wiz/Linux_Other_Cli_MSTest_GitHubActions.md +++ b/docs/wiz/Linux_Other_Cli_MSTest_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_MSTest_None.md b/docs/wiz/Linux_Other_Cli_MSTest_None.md index 24df7cfd66..79587d28cb 100644 --- a/docs/wiz/Linux_Other_Cli_MSTest_None.md +++ b/docs/wiz/Linux_Other_Cli_MSTest_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_NUnit_AppVeyor.md b/docs/wiz/Linux_Other_Cli_NUnit_AppVeyor.md index 77c0f6cdec..e9f4bfc86f 100644 --- a/docs/wiz/Linux_Other_Cli_NUnit_AppVeyor.md +++ b/docs/wiz/Linux_Other_Cli_NUnit_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_NUnit_AzureDevOps.md b/docs/wiz/Linux_Other_Cli_NUnit_AzureDevOps.md index ecc6456260..b490059877 100644 --- a/docs/wiz/Linux_Other_Cli_NUnit_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Cli_NUnit_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_NUnit_GitHubActions.md b/docs/wiz/Linux_Other_Cli_NUnit_GitHubActions.md index dcc0632d5e..d74c0914fd 100644 --- a/docs/wiz/Linux_Other_Cli_NUnit_GitHubActions.md +++ b/docs/wiz/Linux_Other_Cli_NUnit_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_NUnit_None.md b/docs/wiz/Linux_Other_Cli_NUnit_None.md index a1a08df944..be2e881d74 100644 --- a/docs/wiz/Linux_Other_Cli_NUnit_None.md +++ b/docs/wiz/Linux_Other_Cli_NUnit_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_TUnit_AppVeyor.md b/docs/wiz/Linux_Other_Cli_TUnit_AppVeyor.md index ffbf7decb1..4d8e3d0edf 100644 --- a/docs/wiz/Linux_Other_Cli_TUnit_AppVeyor.md +++ b/docs/wiz/Linux_Other_Cli_TUnit_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_TUnit_AzureDevOps.md b/docs/wiz/Linux_Other_Cli_TUnit_AzureDevOps.md index 57145fafba..d03ff613bf 100644 --- a/docs/wiz/Linux_Other_Cli_TUnit_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Cli_TUnit_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_TUnit_GitHubActions.md b/docs/wiz/Linux_Other_Cli_TUnit_GitHubActions.md index fbd033279a..94473b528e 100644 --- a/docs/wiz/Linux_Other_Cli_TUnit_GitHubActions.md +++ b/docs/wiz/Linux_Other_Cli_TUnit_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_TUnit_None.md b/docs/wiz/Linux_Other_Cli_TUnit_None.md index 85a06183be..5fda0b0e41 100644 --- a/docs/wiz/Linux_Other_Cli_TUnit_None.md +++ b/docs/wiz/Linux_Other_Cli_TUnit_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_XunitV3_AppVeyor.md b/docs/wiz/Linux_Other_Cli_XunitV3_AppVeyor.md index e7e4985f91..797737b940 100644 --- a/docs/wiz/Linux_Other_Cli_XunitV3_AppVeyor.md +++ b/docs/wiz/Linux_Other_Cli_XunitV3_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_XunitV3_AzureDevOps.md b/docs/wiz/Linux_Other_Cli_XunitV3_AzureDevOps.md index ee16358925..483e14fdcd 100644 --- a/docs/wiz/Linux_Other_Cli_XunitV3_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Cli_XunitV3_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_XunitV3_GitHubActions.md b/docs/wiz/Linux_Other_Cli_XunitV3_GitHubActions.md index 0eef381018..1a10a7173f 100644 --- a/docs/wiz/Linux_Other_Cli_XunitV3_GitHubActions.md +++ b/docs/wiz/Linux_Other_Cli_XunitV3_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Cli_XunitV3_None.md b/docs/wiz/Linux_Other_Cli_XunitV3_None.md index 9296627415..b5f9af4210 100644 --- a/docs/wiz/Linux_Other_Cli_XunitV3_None.md +++ b/docs/wiz/Linux_Other_Cli_XunitV3_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_Expecto_AppVeyor.md b/docs/wiz/Linux_Other_Gui_Expecto_AppVeyor.md index 362458bacb..dd59e5b249 100644 --- a/docs/wiz/Linux_Other_Gui_Expecto_AppVeyor.md +++ b/docs/wiz/Linux_Other_Gui_Expecto_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_Expecto_AzureDevOps.md b/docs/wiz/Linux_Other_Gui_Expecto_AzureDevOps.md index 4a8f70cc09..d9ad79c725 100644 --- a/docs/wiz/Linux_Other_Gui_Expecto_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Gui_Expecto_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_Expecto_GitHubActions.md b/docs/wiz/Linux_Other_Gui_Expecto_GitHubActions.md index 7e5263e325..916d38028a 100644 --- a/docs/wiz/Linux_Other_Gui_Expecto_GitHubActions.md +++ b/docs/wiz/Linux_Other_Gui_Expecto_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_Expecto_None.md b/docs/wiz/Linux_Other_Gui_Expecto_None.md index 9f4858a784..28712a7293 100644 --- a/docs/wiz/Linux_Other_Gui_Expecto_None.md +++ b/docs/wiz/Linux_Other_Gui_Expecto_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_Fixie_AppVeyor.md b/docs/wiz/Linux_Other_Gui_Fixie_AppVeyor.md index 2fde652fa7..1c85ddbb87 100644 --- a/docs/wiz/Linux_Other_Gui_Fixie_AppVeyor.md +++ b/docs/wiz/Linux_Other_Gui_Fixie_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_Fixie_AzureDevOps.md b/docs/wiz/Linux_Other_Gui_Fixie_AzureDevOps.md index a5dd34c28e..e0487d6d50 100644 --- a/docs/wiz/Linux_Other_Gui_Fixie_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Gui_Fixie_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_Fixie_GitHubActions.md b/docs/wiz/Linux_Other_Gui_Fixie_GitHubActions.md index 1fde0efc53..f8b6ab6f5c 100644 --- a/docs/wiz/Linux_Other_Gui_Fixie_GitHubActions.md +++ b/docs/wiz/Linux_Other_Gui_Fixie_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_Fixie_None.md b/docs/wiz/Linux_Other_Gui_Fixie_None.md index e40ec743e4..fba5288a7c 100644 --- a/docs/wiz/Linux_Other_Gui_Fixie_None.md +++ b/docs/wiz/Linux_Other_Gui_Fixie_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_MSTest_AppVeyor.md b/docs/wiz/Linux_Other_Gui_MSTest_AppVeyor.md index a4d4e9377c..301245650e 100644 --- a/docs/wiz/Linux_Other_Gui_MSTest_AppVeyor.md +++ b/docs/wiz/Linux_Other_Gui_MSTest_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_MSTest_AzureDevOps.md b/docs/wiz/Linux_Other_Gui_MSTest_AzureDevOps.md index 7b4426feca..b31c9a140f 100644 --- a/docs/wiz/Linux_Other_Gui_MSTest_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Gui_MSTest_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_MSTest_GitHubActions.md b/docs/wiz/Linux_Other_Gui_MSTest_GitHubActions.md index 3a5ccc0ae7..55c5dcb555 100644 --- a/docs/wiz/Linux_Other_Gui_MSTest_GitHubActions.md +++ b/docs/wiz/Linux_Other_Gui_MSTest_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_MSTest_None.md b/docs/wiz/Linux_Other_Gui_MSTest_None.md index 5cc4fee410..104bb32c3e 100644 --- a/docs/wiz/Linux_Other_Gui_MSTest_None.md +++ b/docs/wiz/Linux_Other_Gui_MSTest_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_NUnit_AppVeyor.md b/docs/wiz/Linux_Other_Gui_NUnit_AppVeyor.md index 761d21b733..624b97a249 100644 --- a/docs/wiz/Linux_Other_Gui_NUnit_AppVeyor.md +++ b/docs/wiz/Linux_Other_Gui_NUnit_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_NUnit_AzureDevOps.md b/docs/wiz/Linux_Other_Gui_NUnit_AzureDevOps.md index 78b76f3479..35a4bcf734 100644 --- a/docs/wiz/Linux_Other_Gui_NUnit_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Gui_NUnit_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_NUnit_GitHubActions.md b/docs/wiz/Linux_Other_Gui_NUnit_GitHubActions.md index 98cf34fcb3..eaeb89337e 100644 --- a/docs/wiz/Linux_Other_Gui_NUnit_GitHubActions.md +++ b/docs/wiz/Linux_Other_Gui_NUnit_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_NUnit_None.md b/docs/wiz/Linux_Other_Gui_NUnit_None.md index 3d3c5659e5..2e23d7e95a 100644 --- a/docs/wiz/Linux_Other_Gui_NUnit_None.md +++ b/docs/wiz/Linux_Other_Gui_NUnit_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_TUnit_AppVeyor.md b/docs/wiz/Linux_Other_Gui_TUnit_AppVeyor.md index 67c8957213..1baea28931 100644 --- a/docs/wiz/Linux_Other_Gui_TUnit_AppVeyor.md +++ b/docs/wiz/Linux_Other_Gui_TUnit_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_TUnit_AzureDevOps.md b/docs/wiz/Linux_Other_Gui_TUnit_AzureDevOps.md index b2e283a6a1..d434865379 100644 --- a/docs/wiz/Linux_Other_Gui_TUnit_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Gui_TUnit_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_TUnit_GitHubActions.md b/docs/wiz/Linux_Other_Gui_TUnit_GitHubActions.md index 1cc241fab0..87ffb7e3f0 100644 --- a/docs/wiz/Linux_Other_Gui_TUnit_GitHubActions.md +++ b/docs/wiz/Linux_Other_Gui_TUnit_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_TUnit_None.md b/docs/wiz/Linux_Other_Gui_TUnit_None.md index d6bcd6f045..d173f5c9db 100644 --- a/docs/wiz/Linux_Other_Gui_TUnit_None.md +++ b/docs/wiz/Linux_Other_Gui_TUnit_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_XunitV3_AppVeyor.md b/docs/wiz/Linux_Other_Gui_XunitV3_AppVeyor.md index 5a744b9977..63a0a959f9 100644 --- a/docs/wiz/Linux_Other_Gui_XunitV3_AppVeyor.md +++ b/docs/wiz/Linux_Other_Gui_XunitV3_AppVeyor.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_XunitV3_AzureDevOps.md b/docs/wiz/Linux_Other_Gui_XunitV3_AzureDevOps.md index 622c6a5927..a6e3d80530 100644 --- a/docs/wiz/Linux_Other_Gui_XunitV3_AzureDevOps.md +++ b/docs/wiz/Linux_Other_Gui_XunitV3_AzureDevOps.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_XunitV3_GitHubActions.md b/docs/wiz/Linux_Other_Gui_XunitV3_GitHubActions.md index 8e0b5cf697..ecc6077262 100644 --- a/docs/wiz/Linux_Other_Gui_XunitV3_GitHubActions.md +++ b/docs/wiz/Linux_Other_Gui_XunitV3_GitHubActions.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Other_Gui_XunitV3_None.md b/docs/wiz/Linux_Other_Gui_XunitV3_None.md index 0863ae8ec4..c1478f2b2d 100644 --- a/docs/wiz/Linux_Other_Gui_XunitV3_None.md +++ b/docs/wiz/Linux_Other_Gui_XunitV3_None.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_Expecto_AppVeyor.md b/docs/wiz/Linux_Rider_Cli_Expecto_AppVeyor.md index 3824b18205..776ee27004 100644 --- a/docs/wiz/Linux_Rider_Cli_Expecto_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Cli_Expecto_AppVeyor.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_Expecto_AzureDevOps.md b/docs/wiz/Linux_Rider_Cli_Expecto_AzureDevOps.md index 4b76117aa4..4142b029eb 100644 --- a/docs/wiz/Linux_Rider_Cli_Expecto_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Cli_Expecto_AzureDevOps.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_Expecto_GitHubActions.md b/docs/wiz/Linux_Rider_Cli_Expecto_GitHubActions.md index 1c3a023d0b..9fec5398e0 100644 --- a/docs/wiz/Linux_Rider_Cli_Expecto_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Cli_Expecto_GitHubActions.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_Expecto_None.md b/docs/wiz/Linux_Rider_Cli_Expecto_None.md index 2372ebd4f5..69205a12a0 100644 --- a/docs/wiz/Linux_Rider_Cli_Expecto_None.md +++ b/docs/wiz/Linux_Rider_Cli_Expecto_None.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_Fixie_AppVeyor.md b/docs/wiz/Linux_Rider_Cli_Fixie_AppVeyor.md index c6ead5db4a..d8d08bc1a2 100644 --- a/docs/wiz/Linux_Rider_Cli_Fixie_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Cli_Fixie_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_Fixie_AzureDevOps.md b/docs/wiz/Linux_Rider_Cli_Fixie_AzureDevOps.md index bb5de60b97..13fe6e4d0d 100644 --- a/docs/wiz/Linux_Rider_Cli_Fixie_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Cli_Fixie_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_Fixie_GitHubActions.md b/docs/wiz/Linux_Rider_Cli_Fixie_GitHubActions.md index b2f3dcacb3..d80baf23ee 100644 --- a/docs/wiz/Linux_Rider_Cli_Fixie_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Cli_Fixie_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_Fixie_None.md b/docs/wiz/Linux_Rider_Cli_Fixie_None.md index 3bd62ea1a3..bb28ac14e8 100644 --- a/docs/wiz/Linux_Rider_Cli_Fixie_None.md +++ b/docs/wiz/Linux_Rider_Cli_Fixie_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_MSTest_AppVeyor.md b/docs/wiz/Linux_Rider_Cli_MSTest_AppVeyor.md index 39d60e5230..bf45f544be 100644 --- a/docs/wiz/Linux_Rider_Cli_MSTest_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Cli_MSTest_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_MSTest_AzureDevOps.md b/docs/wiz/Linux_Rider_Cli_MSTest_AzureDevOps.md index fc1b6e108b..889f8eab2b 100644 --- a/docs/wiz/Linux_Rider_Cli_MSTest_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Cli_MSTest_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_MSTest_GitHubActions.md b/docs/wiz/Linux_Rider_Cli_MSTest_GitHubActions.md index 247819ad56..fb7f38e339 100644 --- a/docs/wiz/Linux_Rider_Cli_MSTest_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Cli_MSTest_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_MSTest_None.md b/docs/wiz/Linux_Rider_Cli_MSTest_None.md index 8ff1abd264..f561d8fde5 100644 --- a/docs/wiz/Linux_Rider_Cli_MSTest_None.md +++ b/docs/wiz/Linux_Rider_Cli_MSTest_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_NUnit_AppVeyor.md b/docs/wiz/Linux_Rider_Cli_NUnit_AppVeyor.md index 8c1c34908b..43283fc7a9 100644 --- a/docs/wiz/Linux_Rider_Cli_NUnit_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Cli_NUnit_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_NUnit_AzureDevOps.md b/docs/wiz/Linux_Rider_Cli_NUnit_AzureDevOps.md index 5ab471f960..bff33f7a6c 100644 --- a/docs/wiz/Linux_Rider_Cli_NUnit_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Cli_NUnit_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_NUnit_GitHubActions.md b/docs/wiz/Linux_Rider_Cli_NUnit_GitHubActions.md index acc9fa5bb5..080bf49ba6 100644 --- a/docs/wiz/Linux_Rider_Cli_NUnit_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Cli_NUnit_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_NUnit_None.md b/docs/wiz/Linux_Rider_Cli_NUnit_None.md index f47ac46b80..43071675d1 100644 --- a/docs/wiz/Linux_Rider_Cli_NUnit_None.md +++ b/docs/wiz/Linux_Rider_Cli_NUnit_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_TUnit_AppVeyor.md b/docs/wiz/Linux_Rider_Cli_TUnit_AppVeyor.md index 194530853d..fd0e0e6a97 100644 --- a/docs/wiz/Linux_Rider_Cli_TUnit_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Cli_TUnit_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_TUnit_AzureDevOps.md b/docs/wiz/Linux_Rider_Cli_TUnit_AzureDevOps.md index 3bee2c1ea4..8bcd904c9c 100644 --- a/docs/wiz/Linux_Rider_Cli_TUnit_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Cli_TUnit_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_TUnit_GitHubActions.md b/docs/wiz/Linux_Rider_Cli_TUnit_GitHubActions.md index 388c71a7cf..d710401a6a 100644 --- a/docs/wiz/Linux_Rider_Cli_TUnit_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Cli_TUnit_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_TUnit_None.md b/docs/wiz/Linux_Rider_Cli_TUnit_None.md index e42e5ab3bb..c917c0eab0 100644 --- a/docs/wiz/Linux_Rider_Cli_TUnit_None.md +++ b/docs/wiz/Linux_Rider_Cli_TUnit_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_XunitV3_AppVeyor.md b/docs/wiz/Linux_Rider_Cli_XunitV3_AppVeyor.md index 8b5ea04b8a..20ee23ec0c 100644 --- a/docs/wiz/Linux_Rider_Cli_XunitV3_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Cli_XunitV3_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_XunitV3_AzureDevOps.md b/docs/wiz/Linux_Rider_Cli_XunitV3_AzureDevOps.md index f09aa3ebd9..9e4757f866 100644 --- a/docs/wiz/Linux_Rider_Cli_XunitV3_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Cli_XunitV3_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_XunitV3_GitHubActions.md b/docs/wiz/Linux_Rider_Cli_XunitV3_GitHubActions.md index a61db64e86..13b1c7e3c5 100644 --- a/docs/wiz/Linux_Rider_Cli_XunitV3_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Cli_XunitV3_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Cli_XunitV3_None.md b/docs/wiz/Linux_Rider_Cli_XunitV3_None.md index 2034710ae4..69fb85b8d8 100644 --- a/docs/wiz/Linux_Rider_Cli_XunitV3_None.md +++ b/docs/wiz/Linux_Rider_Cli_XunitV3_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_Expecto_AppVeyor.md b/docs/wiz/Linux_Rider_Gui_Expecto_AppVeyor.md index 0bdf9aa028..47a774baea 100644 --- a/docs/wiz/Linux_Rider_Gui_Expecto_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Gui_Expecto_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_Expecto_AzureDevOps.md b/docs/wiz/Linux_Rider_Gui_Expecto_AzureDevOps.md index 03136cd03f..8a5e1d6864 100644 --- a/docs/wiz/Linux_Rider_Gui_Expecto_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Gui_Expecto_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_Expecto_GitHubActions.md b/docs/wiz/Linux_Rider_Gui_Expecto_GitHubActions.md index ad2288a1c4..2d6fe4cef3 100644 --- a/docs/wiz/Linux_Rider_Gui_Expecto_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Gui_Expecto_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_Expecto_None.md b/docs/wiz/Linux_Rider_Gui_Expecto_None.md index f4f57414f1..1fc53d374f 100644 --- a/docs/wiz/Linux_Rider_Gui_Expecto_None.md +++ b/docs/wiz/Linux_Rider_Gui_Expecto_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_Fixie_AppVeyor.md b/docs/wiz/Linux_Rider_Gui_Fixie_AppVeyor.md index 2ba5114143..b0e9b1275b 100644 --- a/docs/wiz/Linux_Rider_Gui_Fixie_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Gui_Fixie_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_Fixie_AzureDevOps.md b/docs/wiz/Linux_Rider_Gui_Fixie_AzureDevOps.md index eeaa03ce0f..813d3a40bc 100644 --- a/docs/wiz/Linux_Rider_Gui_Fixie_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Gui_Fixie_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_Fixie_GitHubActions.md b/docs/wiz/Linux_Rider_Gui_Fixie_GitHubActions.md index 2def889238..0982d4a0ed 100644 --- a/docs/wiz/Linux_Rider_Gui_Fixie_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Gui_Fixie_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_Fixie_None.md b/docs/wiz/Linux_Rider_Gui_Fixie_None.md index 14e0861158..756edeaff9 100644 --- a/docs/wiz/Linux_Rider_Gui_Fixie_None.md +++ b/docs/wiz/Linux_Rider_Gui_Fixie_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_MSTest_AppVeyor.md b/docs/wiz/Linux_Rider_Gui_MSTest_AppVeyor.md index 76fd4803ab..ace7d620ee 100644 --- a/docs/wiz/Linux_Rider_Gui_MSTest_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Gui_MSTest_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_MSTest_AzureDevOps.md b/docs/wiz/Linux_Rider_Gui_MSTest_AzureDevOps.md index d1fe420754..6939044eb6 100644 --- a/docs/wiz/Linux_Rider_Gui_MSTest_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Gui_MSTest_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_MSTest_GitHubActions.md b/docs/wiz/Linux_Rider_Gui_MSTest_GitHubActions.md index 218b8e5ae8..04a0390f58 100644 --- a/docs/wiz/Linux_Rider_Gui_MSTest_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Gui_MSTest_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_MSTest_None.md b/docs/wiz/Linux_Rider_Gui_MSTest_None.md index 326aa984c6..6673af3fa4 100644 --- a/docs/wiz/Linux_Rider_Gui_MSTest_None.md +++ b/docs/wiz/Linux_Rider_Gui_MSTest_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_NUnit_AppVeyor.md b/docs/wiz/Linux_Rider_Gui_NUnit_AppVeyor.md index 5eb70659c9..e1658ed370 100644 --- a/docs/wiz/Linux_Rider_Gui_NUnit_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Gui_NUnit_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_NUnit_AzureDevOps.md b/docs/wiz/Linux_Rider_Gui_NUnit_AzureDevOps.md index 86fae80f2e..53089c9607 100644 --- a/docs/wiz/Linux_Rider_Gui_NUnit_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Gui_NUnit_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_NUnit_GitHubActions.md b/docs/wiz/Linux_Rider_Gui_NUnit_GitHubActions.md index a1db42b712..2e61cb6f98 100644 --- a/docs/wiz/Linux_Rider_Gui_NUnit_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Gui_NUnit_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_NUnit_None.md b/docs/wiz/Linux_Rider_Gui_NUnit_None.md index 60b55b8c52..eb3d4a0c29 100644 --- a/docs/wiz/Linux_Rider_Gui_NUnit_None.md +++ b/docs/wiz/Linux_Rider_Gui_NUnit_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_TUnit_AppVeyor.md b/docs/wiz/Linux_Rider_Gui_TUnit_AppVeyor.md index 3a2cf4c674..ac89270092 100644 --- a/docs/wiz/Linux_Rider_Gui_TUnit_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Gui_TUnit_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_TUnit_AzureDevOps.md b/docs/wiz/Linux_Rider_Gui_TUnit_AzureDevOps.md index 32715247c8..69ee49921c 100644 --- a/docs/wiz/Linux_Rider_Gui_TUnit_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Gui_TUnit_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_TUnit_GitHubActions.md b/docs/wiz/Linux_Rider_Gui_TUnit_GitHubActions.md index 342aa954c7..1e2be92411 100644 --- a/docs/wiz/Linux_Rider_Gui_TUnit_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Gui_TUnit_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_TUnit_None.md b/docs/wiz/Linux_Rider_Gui_TUnit_None.md index ef473865e8..38b9e0bb08 100644 --- a/docs/wiz/Linux_Rider_Gui_TUnit_None.md +++ b/docs/wiz/Linux_Rider_Gui_TUnit_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_XunitV3_AppVeyor.md b/docs/wiz/Linux_Rider_Gui_XunitV3_AppVeyor.md index 9311367fb3..ff7b8e5904 100644 --- a/docs/wiz/Linux_Rider_Gui_XunitV3_AppVeyor.md +++ b/docs/wiz/Linux_Rider_Gui_XunitV3_AppVeyor.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_XunitV3_AzureDevOps.md b/docs/wiz/Linux_Rider_Gui_XunitV3_AzureDevOps.md index 2353fa84da..d6829a29c7 100644 --- a/docs/wiz/Linux_Rider_Gui_XunitV3_AzureDevOps.md +++ b/docs/wiz/Linux_Rider_Gui_XunitV3_AzureDevOps.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_XunitV3_GitHubActions.md b/docs/wiz/Linux_Rider_Gui_XunitV3_GitHubActions.md index cb718c3bc5..53a6576ca9 100644 --- a/docs/wiz/Linux_Rider_Gui_XunitV3_GitHubActions.md +++ b/docs/wiz/Linux_Rider_Gui_XunitV3_GitHubActions.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Linux_Rider_Gui_XunitV3_None.md b/docs/wiz/Linux_Rider_Gui_XunitV3_None.md index 8e3541f18f..d2b2852659 100644 --- a/docs/wiz/Linux_Rider_Gui_XunitV3_None.md +++ b/docs/wiz/Linux_Rider_Gui_XunitV3_None.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_Expecto_AppVeyor.md b/docs/wiz/MacOS_Other_Cli_Expecto_AppVeyor.md index eeb3c638c0..053708f306 100644 --- a/docs/wiz/MacOS_Other_Cli_Expecto_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Cli_Expecto_AppVeyor.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_Expecto_AzureDevOps.md b/docs/wiz/MacOS_Other_Cli_Expecto_AzureDevOps.md index 518ed3d670..201e01766f 100644 --- a/docs/wiz/MacOS_Other_Cli_Expecto_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Cli_Expecto_AzureDevOps.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_Expecto_GitHubActions.md b/docs/wiz/MacOS_Other_Cli_Expecto_GitHubActions.md index d1a2d474b1..4da0448308 100644 --- a/docs/wiz/MacOS_Other_Cli_Expecto_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Cli_Expecto_GitHubActions.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_Expecto_None.md b/docs/wiz/MacOS_Other_Cli_Expecto_None.md index c2579b2391..c32b537c97 100644 --- a/docs/wiz/MacOS_Other_Cli_Expecto_None.md +++ b/docs/wiz/MacOS_Other_Cli_Expecto_None.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_Fixie_AppVeyor.md b/docs/wiz/MacOS_Other_Cli_Fixie_AppVeyor.md index 16672d9915..432a327411 100644 --- a/docs/wiz/MacOS_Other_Cli_Fixie_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Cli_Fixie_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_Fixie_AzureDevOps.md b/docs/wiz/MacOS_Other_Cli_Fixie_AzureDevOps.md index 7f42bd0c3e..d83859486c 100644 --- a/docs/wiz/MacOS_Other_Cli_Fixie_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Cli_Fixie_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_Fixie_GitHubActions.md b/docs/wiz/MacOS_Other_Cli_Fixie_GitHubActions.md index dd08fc9a8d..aafeaf1970 100644 --- a/docs/wiz/MacOS_Other_Cli_Fixie_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Cli_Fixie_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_Fixie_None.md b/docs/wiz/MacOS_Other_Cli_Fixie_None.md index ac9afc6c7b..d510f5c25e 100644 --- a/docs/wiz/MacOS_Other_Cli_Fixie_None.md +++ b/docs/wiz/MacOS_Other_Cli_Fixie_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_MSTest_AppVeyor.md b/docs/wiz/MacOS_Other_Cli_MSTest_AppVeyor.md index 2a0ee72095..d72cf44606 100644 --- a/docs/wiz/MacOS_Other_Cli_MSTest_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Cli_MSTest_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_MSTest_AzureDevOps.md b/docs/wiz/MacOS_Other_Cli_MSTest_AzureDevOps.md index aba5757d70..6771c71f12 100644 --- a/docs/wiz/MacOS_Other_Cli_MSTest_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Cli_MSTest_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_MSTest_GitHubActions.md b/docs/wiz/MacOS_Other_Cli_MSTest_GitHubActions.md index 3ae3bb0007..4e78eb26c5 100644 --- a/docs/wiz/MacOS_Other_Cli_MSTest_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Cli_MSTest_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_MSTest_None.md b/docs/wiz/MacOS_Other_Cli_MSTest_None.md index 2ddb941595..df77bb3e02 100644 --- a/docs/wiz/MacOS_Other_Cli_MSTest_None.md +++ b/docs/wiz/MacOS_Other_Cli_MSTest_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_NUnit_AppVeyor.md b/docs/wiz/MacOS_Other_Cli_NUnit_AppVeyor.md index 76b1e13803..05ae8669c5 100644 --- a/docs/wiz/MacOS_Other_Cli_NUnit_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Cli_NUnit_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_NUnit_AzureDevOps.md b/docs/wiz/MacOS_Other_Cli_NUnit_AzureDevOps.md index c01b573634..ef4ab5b416 100644 --- a/docs/wiz/MacOS_Other_Cli_NUnit_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Cli_NUnit_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_NUnit_GitHubActions.md b/docs/wiz/MacOS_Other_Cli_NUnit_GitHubActions.md index f91d6030a1..b9914ac0c1 100644 --- a/docs/wiz/MacOS_Other_Cli_NUnit_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Cli_NUnit_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_NUnit_None.md b/docs/wiz/MacOS_Other_Cli_NUnit_None.md index 5f95d35231..13dce8ebb4 100644 --- a/docs/wiz/MacOS_Other_Cli_NUnit_None.md +++ b/docs/wiz/MacOS_Other_Cli_NUnit_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_TUnit_AppVeyor.md b/docs/wiz/MacOS_Other_Cli_TUnit_AppVeyor.md index 7591ab7f39..de44763b74 100644 --- a/docs/wiz/MacOS_Other_Cli_TUnit_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Cli_TUnit_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_TUnit_AzureDevOps.md b/docs/wiz/MacOS_Other_Cli_TUnit_AzureDevOps.md index 503072a15b..fc797dd24c 100644 --- a/docs/wiz/MacOS_Other_Cli_TUnit_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Cli_TUnit_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_TUnit_GitHubActions.md b/docs/wiz/MacOS_Other_Cli_TUnit_GitHubActions.md index 59d5209db4..1abd077092 100644 --- a/docs/wiz/MacOS_Other_Cli_TUnit_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Cli_TUnit_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_TUnit_None.md b/docs/wiz/MacOS_Other_Cli_TUnit_None.md index f3f1e0f863..3cc9330771 100644 --- a/docs/wiz/MacOS_Other_Cli_TUnit_None.md +++ b/docs/wiz/MacOS_Other_Cli_TUnit_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_XunitV3_AppVeyor.md b/docs/wiz/MacOS_Other_Cli_XunitV3_AppVeyor.md index ae26100af2..28869871ea 100644 --- a/docs/wiz/MacOS_Other_Cli_XunitV3_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Cli_XunitV3_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_XunitV3_AzureDevOps.md b/docs/wiz/MacOS_Other_Cli_XunitV3_AzureDevOps.md index 9f5014b980..3cd6c6d40c 100644 --- a/docs/wiz/MacOS_Other_Cli_XunitV3_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Cli_XunitV3_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_XunitV3_GitHubActions.md b/docs/wiz/MacOS_Other_Cli_XunitV3_GitHubActions.md index b3265ca219..db18719567 100644 --- a/docs/wiz/MacOS_Other_Cli_XunitV3_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Cli_XunitV3_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Cli_XunitV3_None.md b/docs/wiz/MacOS_Other_Cli_XunitV3_None.md index aa83ac01b1..fe13743768 100644 --- a/docs/wiz/MacOS_Other_Cli_XunitV3_None.md +++ b/docs/wiz/MacOS_Other_Cli_XunitV3_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_Expecto_AppVeyor.md b/docs/wiz/MacOS_Other_Gui_Expecto_AppVeyor.md index 818160d08c..0af3966c56 100644 --- a/docs/wiz/MacOS_Other_Gui_Expecto_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Gui_Expecto_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_Expecto_AzureDevOps.md b/docs/wiz/MacOS_Other_Gui_Expecto_AzureDevOps.md index 6abe85c937..5f5a8018d3 100644 --- a/docs/wiz/MacOS_Other_Gui_Expecto_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Gui_Expecto_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_Expecto_GitHubActions.md b/docs/wiz/MacOS_Other_Gui_Expecto_GitHubActions.md index 69029ec851..4274281c6d 100644 --- a/docs/wiz/MacOS_Other_Gui_Expecto_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Gui_Expecto_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_Expecto_None.md b/docs/wiz/MacOS_Other_Gui_Expecto_None.md index c5e87516c2..4fb6cea4d7 100644 --- a/docs/wiz/MacOS_Other_Gui_Expecto_None.md +++ b/docs/wiz/MacOS_Other_Gui_Expecto_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_Fixie_AppVeyor.md b/docs/wiz/MacOS_Other_Gui_Fixie_AppVeyor.md index d6bedbac6c..8e6bc974f9 100644 --- a/docs/wiz/MacOS_Other_Gui_Fixie_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Gui_Fixie_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_Fixie_AzureDevOps.md b/docs/wiz/MacOS_Other_Gui_Fixie_AzureDevOps.md index 893e3df269..3eb822faaa 100644 --- a/docs/wiz/MacOS_Other_Gui_Fixie_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Gui_Fixie_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_Fixie_GitHubActions.md b/docs/wiz/MacOS_Other_Gui_Fixie_GitHubActions.md index e52534095a..cd5b05a68e 100644 --- a/docs/wiz/MacOS_Other_Gui_Fixie_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Gui_Fixie_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_Fixie_None.md b/docs/wiz/MacOS_Other_Gui_Fixie_None.md index 63da6931a8..937f92bc81 100644 --- a/docs/wiz/MacOS_Other_Gui_Fixie_None.md +++ b/docs/wiz/MacOS_Other_Gui_Fixie_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_MSTest_AppVeyor.md b/docs/wiz/MacOS_Other_Gui_MSTest_AppVeyor.md index c0b6c863ce..e284a49f7e 100644 --- a/docs/wiz/MacOS_Other_Gui_MSTest_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Gui_MSTest_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_MSTest_AzureDevOps.md b/docs/wiz/MacOS_Other_Gui_MSTest_AzureDevOps.md index 38bc1e5a26..aef509edf0 100644 --- a/docs/wiz/MacOS_Other_Gui_MSTest_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Gui_MSTest_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_MSTest_GitHubActions.md b/docs/wiz/MacOS_Other_Gui_MSTest_GitHubActions.md index 7ec3fa1ad4..561e975a27 100644 --- a/docs/wiz/MacOS_Other_Gui_MSTest_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Gui_MSTest_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_MSTest_None.md b/docs/wiz/MacOS_Other_Gui_MSTest_None.md index 05ae2e938e..ea53330d1d 100644 --- a/docs/wiz/MacOS_Other_Gui_MSTest_None.md +++ b/docs/wiz/MacOS_Other_Gui_MSTest_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_NUnit_AppVeyor.md b/docs/wiz/MacOS_Other_Gui_NUnit_AppVeyor.md index 6585d7b789..c3c76ff115 100644 --- a/docs/wiz/MacOS_Other_Gui_NUnit_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Gui_NUnit_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_NUnit_AzureDevOps.md b/docs/wiz/MacOS_Other_Gui_NUnit_AzureDevOps.md index d0418e9e4a..76d17ced2f 100644 --- a/docs/wiz/MacOS_Other_Gui_NUnit_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Gui_NUnit_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_NUnit_GitHubActions.md b/docs/wiz/MacOS_Other_Gui_NUnit_GitHubActions.md index 2f5cbe3f7e..c9f960744c 100644 --- a/docs/wiz/MacOS_Other_Gui_NUnit_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Gui_NUnit_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_NUnit_None.md b/docs/wiz/MacOS_Other_Gui_NUnit_None.md index b7e3920222..9fcd589bbf 100644 --- a/docs/wiz/MacOS_Other_Gui_NUnit_None.md +++ b/docs/wiz/MacOS_Other_Gui_NUnit_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_TUnit_AppVeyor.md b/docs/wiz/MacOS_Other_Gui_TUnit_AppVeyor.md index 5b5ebe65e3..d1a89da947 100644 --- a/docs/wiz/MacOS_Other_Gui_TUnit_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Gui_TUnit_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_TUnit_AzureDevOps.md b/docs/wiz/MacOS_Other_Gui_TUnit_AzureDevOps.md index 317118f895..237ca0cb17 100644 --- a/docs/wiz/MacOS_Other_Gui_TUnit_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Gui_TUnit_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_TUnit_GitHubActions.md b/docs/wiz/MacOS_Other_Gui_TUnit_GitHubActions.md index d834f0eb66..d3b8dc16ab 100644 --- a/docs/wiz/MacOS_Other_Gui_TUnit_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Gui_TUnit_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_TUnit_None.md b/docs/wiz/MacOS_Other_Gui_TUnit_None.md index b77788615a..78023b33a8 100644 --- a/docs/wiz/MacOS_Other_Gui_TUnit_None.md +++ b/docs/wiz/MacOS_Other_Gui_TUnit_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_XunitV3_AppVeyor.md b/docs/wiz/MacOS_Other_Gui_XunitV3_AppVeyor.md index 5fa179186a..312093dcd2 100644 --- a/docs/wiz/MacOS_Other_Gui_XunitV3_AppVeyor.md +++ b/docs/wiz/MacOS_Other_Gui_XunitV3_AppVeyor.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_XunitV3_AzureDevOps.md b/docs/wiz/MacOS_Other_Gui_XunitV3_AzureDevOps.md index 379fc28e89..d2ce82c606 100644 --- a/docs/wiz/MacOS_Other_Gui_XunitV3_AzureDevOps.md +++ b/docs/wiz/MacOS_Other_Gui_XunitV3_AzureDevOps.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_XunitV3_GitHubActions.md b/docs/wiz/MacOS_Other_Gui_XunitV3_GitHubActions.md index 27c3df9223..88526e07cc 100644 --- a/docs/wiz/MacOS_Other_Gui_XunitV3_GitHubActions.md +++ b/docs/wiz/MacOS_Other_Gui_XunitV3_GitHubActions.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Other_Gui_XunitV3_None.md b/docs/wiz/MacOS_Other_Gui_XunitV3_None.md index 1a66451a34..333587659e 100644 --- a/docs/wiz/MacOS_Other_Gui_XunitV3_None.md +++ b/docs/wiz/MacOS_Other_Gui_XunitV3_None.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_Expecto_AppVeyor.md b/docs/wiz/MacOS_Rider_Cli_Expecto_AppVeyor.md index 826c96736f..3680e82f0c 100644 --- a/docs/wiz/MacOS_Rider_Cli_Expecto_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Cli_Expecto_AppVeyor.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_Expecto_AzureDevOps.md b/docs/wiz/MacOS_Rider_Cli_Expecto_AzureDevOps.md index e8ae36974b..22b3811631 100644 --- a/docs/wiz/MacOS_Rider_Cli_Expecto_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Cli_Expecto_AzureDevOps.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_Expecto_GitHubActions.md b/docs/wiz/MacOS_Rider_Cli_Expecto_GitHubActions.md index 8de344a313..630edd5e0b 100644 --- a/docs/wiz/MacOS_Rider_Cli_Expecto_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Cli_Expecto_GitHubActions.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_Expecto_None.md b/docs/wiz/MacOS_Rider_Cli_Expecto_None.md index 7a65dfb5e6..8d1328f1ae 100644 --- a/docs/wiz/MacOS_Rider_Cli_Expecto_None.md +++ b/docs/wiz/MacOS_Rider_Cli_Expecto_None.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_Fixie_AppVeyor.md b/docs/wiz/MacOS_Rider_Cli_Fixie_AppVeyor.md index a3e9a794fd..d3e1a19bd3 100644 --- a/docs/wiz/MacOS_Rider_Cli_Fixie_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Cli_Fixie_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_Fixie_AzureDevOps.md b/docs/wiz/MacOS_Rider_Cli_Fixie_AzureDevOps.md index 8dbc573569..3bf28ef260 100644 --- a/docs/wiz/MacOS_Rider_Cli_Fixie_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Cli_Fixie_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_Fixie_GitHubActions.md b/docs/wiz/MacOS_Rider_Cli_Fixie_GitHubActions.md index 45c96c4b3a..6e7708a235 100644 --- a/docs/wiz/MacOS_Rider_Cli_Fixie_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Cli_Fixie_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_Fixie_None.md b/docs/wiz/MacOS_Rider_Cli_Fixie_None.md index 5218d7a25c..e3f3416d9f 100644 --- a/docs/wiz/MacOS_Rider_Cli_Fixie_None.md +++ b/docs/wiz/MacOS_Rider_Cli_Fixie_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_MSTest_AppVeyor.md b/docs/wiz/MacOS_Rider_Cli_MSTest_AppVeyor.md index 285d44559b..910e7e907c 100644 --- a/docs/wiz/MacOS_Rider_Cli_MSTest_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Cli_MSTest_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_MSTest_AzureDevOps.md b/docs/wiz/MacOS_Rider_Cli_MSTest_AzureDevOps.md index 2abd102971..b25dd53ec9 100644 --- a/docs/wiz/MacOS_Rider_Cli_MSTest_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Cli_MSTest_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_MSTest_GitHubActions.md b/docs/wiz/MacOS_Rider_Cli_MSTest_GitHubActions.md index 0050e5c614..0a34d06455 100644 --- a/docs/wiz/MacOS_Rider_Cli_MSTest_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Cli_MSTest_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_MSTest_None.md b/docs/wiz/MacOS_Rider_Cli_MSTest_None.md index e0e00bc868..3ce7eb924b 100644 --- a/docs/wiz/MacOS_Rider_Cli_MSTest_None.md +++ b/docs/wiz/MacOS_Rider_Cli_MSTest_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_NUnit_AppVeyor.md b/docs/wiz/MacOS_Rider_Cli_NUnit_AppVeyor.md index 87b82c5124..2a47761c77 100644 --- a/docs/wiz/MacOS_Rider_Cli_NUnit_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Cli_NUnit_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_NUnit_AzureDevOps.md b/docs/wiz/MacOS_Rider_Cli_NUnit_AzureDevOps.md index 3350b85588..3302ff8411 100644 --- a/docs/wiz/MacOS_Rider_Cli_NUnit_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Cli_NUnit_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_NUnit_GitHubActions.md b/docs/wiz/MacOS_Rider_Cli_NUnit_GitHubActions.md index 9d9087e667..a127c92a2f 100644 --- a/docs/wiz/MacOS_Rider_Cli_NUnit_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Cli_NUnit_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_NUnit_None.md b/docs/wiz/MacOS_Rider_Cli_NUnit_None.md index b0a8ce8c20..762efeaa9b 100644 --- a/docs/wiz/MacOS_Rider_Cli_NUnit_None.md +++ b/docs/wiz/MacOS_Rider_Cli_NUnit_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_TUnit_AppVeyor.md b/docs/wiz/MacOS_Rider_Cli_TUnit_AppVeyor.md index d7b7bf2522..4a47ddf47b 100644 --- a/docs/wiz/MacOS_Rider_Cli_TUnit_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Cli_TUnit_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_TUnit_AzureDevOps.md b/docs/wiz/MacOS_Rider_Cli_TUnit_AzureDevOps.md index 83a2797bdd..7ffe17b411 100644 --- a/docs/wiz/MacOS_Rider_Cli_TUnit_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Cli_TUnit_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_TUnit_GitHubActions.md b/docs/wiz/MacOS_Rider_Cli_TUnit_GitHubActions.md index 3c3eb8d8b8..877d794ccb 100644 --- a/docs/wiz/MacOS_Rider_Cli_TUnit_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Cli_TUnit_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_TUnit_None.md b/docs/wiz/MacOS_Rider_Cli_TUnit_None.md index 83a52fdde1..ceb2ad2172 100644 --- a/docs/wiz/MacOS_Rider_Cli_TUnit_None.md +++ b/docs/wiz/MacOS_Rider_Cli_TUnit_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_XunitV3_AppVeyor.md b/docs/wiz/MacOS_Rider_Cli_XunitV3_AppVeyor.md index 14268be113..709183048f 100644 --- a/docs/wiz/MacOS_Rider_Cli_XunitV3_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Cli_XunitV3_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_XunitV3_AzureDevOps.md b/docs/wiz/MacOS_Rider_Cli_XunitV3_AzureDevOps.md index c1228fd97d..93ea5bb733 100644 --- a/docs/wiz/MacOS_Rider_Cli_XunitV3_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Cli_XunitV3_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_XunitV3_GitHubActions.md b/docs/wiz/MacOS_Rider_Cli_XunitV3_GitHubActions.md index e5941d28b9..2de37b2748 100644 --- a/docs/wiz/MacOS_Rider_Cli_XunitV3_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Cli_XunitV3_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Cli_XunitV3_None.md b/docs/wiz/MacOS_Rider_Cli_XunitV3_None.md index 0c78bef224..650c5721fb 100644 --- a/docs/wiz/MacOS_Rider_Cli_XunitV3_None.md +++ b/docs/wiz/MacOS_Rider_Cli_XunitV3_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_Expecto_AppVeyor.md b/docs/wiz/MacOS_Rider_Gui_Expecto_AppVeyor.md index 6db7582563..d3872e52ac 100644 --- a/docs/wiz/MacOS_Rider_Gui_Expecto_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Gui_Expecto_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_Expecto_AzureDevOps.md b/docs/wiz/MacOS_Rider_Gui_Expecto_AzureDevOps.md index 27651820d8..13ca80f4be 100644 --- a/docs/wiz/MacOS_Rider_Gui_Expecto_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Gui_Expecto_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_Expecto_GitHubActions.md b/docs/wiz/MacOS_Rider_Gui_Expecto_GitHubActions.md index 299a533340..c86e8574ed 100644 --- a/docs/wiz/MacOS_Rider_Gui_Expecto_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Gui_Expecto_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_Expecto_None.md b/docs/wiz/MacOS_Rider_Gui_Expecto_None.md index 5ae283ba83..f9b6ef4200 100644 --- a/docs/wiz/MacOS_Rider_Gui_Expecto_None.md +++ b/docs/wiz/MacOS_Rider_Gui_Expecto_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_Fixie_AppVeyor.md b/docs/wiz/MacOS_Rider_Gui_Fixie_AppVeyor.md index 87cbd285e2..c26d2b79b2 100644 --- a/docs/wiz/MacOS_Rider_Gui_Fixie_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Gui_Fixie_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_Fixie_AzureDevOps.md b/docs/wiz/MacOS_Rider_Gui_Fixie_AzureDevOps.md index 97bf5d6799..ce52bf27d0 100644 --- a/docs/wiz/MacOS_Rider_Gui_Fixie_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Gui_Fixie_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_Fixie_GitHubActions.md b/docs/wiz/MacOS_Rider_Gui_Fixie_GitHubActions.md index b5fa750d7c..43b8fd7512 100644 --- a/docs/wiz/MacOS_Rider_Gui_Fixie_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Gui_Fixie_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_Fixie_None.md b/docs/wiz/MacOS_Rider_Gui_Fixie_None.md index 9a20d86271..d2f624e5b6 100644 --- a/docs/wiz/MacOS_Rider_Gui_Fixie_None.md +++ b/docs/wiz/MacOS_Rider_Gui_Fixie_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_MSTest_AppVeyor.md b/docs/wiz/MacOS_Rider_Gui_MSTest_AppVeyor.md index 366d259b8d..b7f6cd3c2f 100644 --- a/docs/wiz/MacOS_Rider_Gui_MSTest_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Gui_MSTest_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_MSTest_AzureDevOps.md b/docs/wiz/MacOS_Rider_Gui_MSTest_AzureDevOps.md index ed86b1a97a..2085a9f79b 100644 --- a/docs/wiz/MacOS_Rider_Gui_MSTest_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Gui_MSTest_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_MSTest_GitHubActions.md b/docs/wiz/MacOS_Rider_Gui_MSTest_GitHubActions.md index 0ad38c612a..810c1b27da 100644 --- a/docs/wiz/MacOS_Rider_Gui_MSTest_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Gui_MSTest_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_MSTest_None.md b/docs/wiz/MacOS_Rider_Gui_MSTest_None.md index 2864481bdd..50d5f9c409 100644 --- a/docs/wiz/MacOS_Rider_Gui_MSTest_None.md +++ b/docs/wiz/MacOS_Rider_Gui_MSTest_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_NUnit_AppVeyor.md b/docs/wiz/MacOS_Rider_Gui_NUnit_AppVeyor.md index 924c315a1b..a23483dc54 100644 --- a/docs/wiz/MacOS_Rider_Gui_NUnit_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Gui_NUnit_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_NUnit_AzureDevOps.md b/docs/wiz/MacOS_Rider_Gui_NUnit_AzureDevOps.md index 6496fa296e..d627c29ccb 100644 --- a/docs/wiz/MacOS_Rider_Gui_NUnit_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Gui_NUnit_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_NUnit_GitHubActions.md b/docs/wiz/MacOS_Rider_Gui_NUnit_GitHubActions.md index 006fbbf536..66f303d792 100644 --- a/docs/wiz/MacOS_Rider_Gui_NUnit_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Gui_NUnit_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_NUnit_None.md b/docs/wiz/MacOS_Rider_Gui_NUnit_None.md index 6a699b89a7..a0190f4dba 100644 --- a/docs/wiz/MacOS_Rider_Gui_NUnit_None.md +++ b/docs/wiz/MacOS_Rider_Gui_NUnit_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_TUnit_AppVeyor.md b/docs/wiz/MacOS_Rider_Gui_TUnit_AppVeyor.md index d11c808357..8d5d3bb4bd 100644 --- a/docs/wiz/MacOS_Rider_Gui_TUnit_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Gui_TUnit_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_TUnit_AzureDevOps.md b/docs/wiz/MacOS_Rider_Gui_TUnit_AzureDevOps.md index b395170d43..3f7e633b28 100644 --- a/docs/wiz/MacOS_Rider_Gui_TUnit_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Gui_TUnit_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_TUnit_GitHubActions.md b/docs/wiz/MacOS_Rider_Gui_TUnit_GitHubActions.md index bfc025989b..7dbb81b5f3 100644 --- a/docs/wiz/MacOS_Rider_Gui_TUnit_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Gui_TUnit_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_TUnit_None.md b/docs/wiz/MacOS_Rider_Gui_TUnit_None.md index b3f33f4d5c..ca98131012 100644 --- a/docs/wiz/MacOS_Rider_Gui_TUnit_None.md +++ b/docs/wiz/MacOS_Rider_Gui_TUnit_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_XunitV3_AppVeyor.md b/docs/wiz/MacOS_Rider_Gui_XunitV3_AppVeyor.md index 6bce034803..baa5f6215b 100644 --- a/docs/wiz/MacOS_Rider_Gui_XunitV3_AppVeyor.md +++ b/docs/wiz/MacOS_Rider_Gui_XunitV3_AppVeyor.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_XunitV3_AzureDevOps.md b/docs/wiz/MacOS_Rider_Gui_XunitV3_AzureDevOps.md index 6acb859b1e..6297e2871e 100644 --- a/docs/wiz/MacOS_Rider_Gui_XunitV3_AzureDevOps.md +++ b/docs/wiz/MacOS_Rider_Gui_XunitV3_AzureDevOps.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_XunitV3_GitHubActions.md b/docs/wiz/MacOS_Rider_Gui_XunitV3_GitHubActions.md index 0648444339..18eed8f01a 100644 --- a/docs/wiz/MacOS_Rider_Gui_XunitV3_GitHubActions.md +++ b/docs/wiz/MacOS_Rider_Gui_XunitV3_GitHubActions.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/MacOS_Rider_Gui_XunitV3_None.md b/docs/wiz/MacOS_Rider_Gui_XunitV3_None.md index 0f2f444440..cf5e807353 100644 --- a/docs/wiz/MacOS_Rider_Gui_XunitV3_None.md +++ b/docs/wiz/MacOS_Rider_Gui_XunitV3_None.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_Expecto_AppVeyor.md b/docs/wiz/Windows_Other_Cli_Expecto_AppVeyor.md index aebe54a276..c0528eb6dc 100644 --- a/docs/wiz/Windows_Other_Cli_Expecto_AppVeyor.md +++ b/docs/wiz/Windows_Other_Cli_Expecto_AppVeyor.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_Expecto_AzureDevOps.md b/docs/wiz/Windows_Other_Cli_Expecto_AzureDevOps.md index 3f4e0fbc26..b54de169f9 100644 --- a/docs/wiz/Windows_Other_Cli_Expecto_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Cli_Expecto_AzureDevOps.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_Expecto_GitHubActions.md b/docs/wiz/Windows_Other_Cli_Expecto_GitHubActions.md index 3b01fde6bf..2d79de9599 100644 --- a/docs/wiz/Windows_Other_Cli_Expecto_GitHubActions.md +++ b/docs/wiz/Windows_Other_Cli_Expecto_GitHubActions.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_Expecto_None.md b/docs/wiz/Windows_Other_Cli_Expecto_None.md index 7bc1a685fa..587975d654 100644 --- a/docs/wiz/Windows_Other_Cli_Expecto_None.md +++ b/docs/wiz/Windows_Other_Cli_Expecto_None.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_Fixie_AppVeyor.md b/docs/wiz/Windows_Other_Cli_Fixie_AppVeyor.md index b4be071395..d4961ff91b 100644 --- a/docs/wiz/Windows_Other_Cli_Fixie_AppVeyor.md +++ b/docs/wiz/Windows_Other_Cli_Fixie_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_Fixie_AzureDevOps.md b/docs/wiz/Windows_Other_Cli_Fixie_AzureDevOps.md index c875ddb2a7..3f5ae839d9 100644 --- a/docs/wiz/Windows_Other_Cli_Fixie_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Cli_Fixie_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_Fixie_GitHubActions.md b/docs/wiz/Windows_Other_Cli_Fixie_GitHubActions.md index 9cbeca73da..1ea185b821 100644 --- a/docs/wiz/Windows_Other_Cli_Fixie_GitHubActions.md +++ b/docs/wiz/Windows_Other_Cli_Fixie_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_Fixie_None.md b/docs/wiz/Windows_Other_Cli_Fixie_None.md index 4a770e5b9d..b65213da5b 100644 --- a/docs/wiz/Windows_Other_Cli_Fixie_None.md +++ b/docs/wiz/Windows_Other_Cli_Fixie_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_MSTest_AppVeyor.md b/docs/wiz/Windows_Other_Cli_MSTest_AppVeyor.md index 1a07cc4659..1e28b8652e 100644 --- a/docs/wiz/Windows_Other_Cli_MSTest_AppVeyor.md +++ b/docs/wiz/Windows_Other_Cli_MSTest_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_MSTest_AzureDevOps.md b/docs/wiz/Windows_Other_Cli_MSTest_AzureDevOps.md index 049459cfbf..2eebf08329 100644 --- a/docs/wiz/Windows_Other_Cli_MSTest_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Cli_MSTest_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_MSTest_GitHubActions.md b/docs/wiz/Windows_Other_Cli_MSTest_GitHubActions.md index 73fd1c8e03..263d350e2c 100644 --- a/docs/wiz/Windows_Other_Cli_MSTest_GitHubActions.md +++ b/docs/wiz/Windows_Other_Cli_MSTest_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_MSTest_None.md b/docs/wiz/Windows_Other_Cli_MSTest_None.md index 158bdb9840..bdb19441de 100644 --- a/docs/wiz/Windows_Other_Cli_MSTest_None.md +++ b/docs/wiz/Windows_Other_Cli_MSTest_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_NUnit_AppVeyor.md b/docs/wiz/Windows_Other_Cli_NUnit_AppVeyor.md index a457307c26..b0c36d0214 100644 --- a/docs/wiz/Windows_Other_Cli_NUnit_AppVeyor.md +++ b/docs/wiz/Windows_Other_Cli_NUnit_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_NUnit_AzureDevOps.md b/docs/wiz/Windows_Other_Cli_NUnit_AzureDevOps.md index 58e4ed72d1..24eb6f6db9 100644 --- a/docs/wiz/Windows_Other_Cli_NUnit_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Cli_NUnit_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_NUnit_GitHubActions.md b/docs/wiz/Windows_Other_Cli_NUnit_GitHubActions.md index 4a5f6bce77..397e67496d 100644 --- a/docs/wiz/Windows_Other_Cli_NUnit_GitHubActions.md +++ b/docs/wiz/Windows_Other_Cli_NUnit_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_NUnit_None.md b/docs/wiz/Windows_Other_Cli_NUnit_None.md index f2738f1ead..790fe721e8 100644 --- a/docs/wiz/Windows_Other_Cli_NUnit_None.md +++ b/docs/wiz/Windows_Other_Cli_NUnit_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_TUnit_AppVeyor.md b/docs/wiz/Windows_Other_Cli_TUnit_AppVeyor.md index c0ca4528fe..b3a02d59e7 100644 --- a/docs/wiz/Windows_Other_Cli_TUnit_AppVeyor.md +++ b/docs/wiz/Windows_Other_Cli_TUnit_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_TUnit_AzureDevOps.md b/docs/wiz/Windows_Other_Cli_TUnit_AzureDevOps.md index 866540ded4..daac17de07 100644 --- a/docs/wiz/Windows_Other_Cli_TUnit_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Cli_TUnit_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_TUnit_GitHubActions.md b/docs/wiz/Windows_Other_Cli_TUnit_GitHubActions.md index cbc3af0405..4ee2da2314 100644 --- a/docs/wiz/Windows_Other_Cli_TUnit_GitHubActions.md +++ b/docs/wiz/Windows_Other_Cli_TUnit_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_TUnit_None.md b/docs/wiz/Windows_Other_Cli_TUnit_None.md index ad8f91c57b..78e0e7fc20 100644 --- a/docs/wiz/Windows_Other_Cli_TUnit_None.md +++ b/docs/wiz/Windows_Other_Cli_TUnit_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_XunitV3_AppVeyor.md b/docs/wiz/Windows_Other_Cli_XunitV3_AppVeyor.md index 14ee1edac4..3954b9c10d 100644 --- a/docs/wiz/Windows_Other_Cli_XunitV3_AppVeyor.md +++ b/docs/wiz/Windows_Other_Cli_XunitV3_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_XunitV3_AzureDevOps.md b/docs/wiz/Windows_Other_Cli_XunitV3_AzureDevOps.md index 44662fac59..21b9994b52 100644 --- a/docs/wiz/Windows_Other_Cli_XunitV3_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Cli_XunitV3_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_XunitV3_GitHubActions.md b/docs/wiz/Windows_Other_Cli_XunitV3_GitHubActions.md index 384f5cee62..8644459ae6 100644 --- a/docs/wiz/Windows_Other_Cli_XunitV3_GitHubActions.md +++ b/docs/wiz/Windows_Other_Cli_XunitV3_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Cli_XunitV3_None.md b/docs/wiz/Windows_Other_Cli_XunitV3_None.md index c8690cacf9..34d3fc5342 100644 --- a/docs/wiz/Windows_Other_Cli_XunitV3_None.md +++ b/docs/wiz/Windows_Other_Cli_XunitV3_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_Expecto_AppVeyor.md b/docs/wiz/Windows_Other_Gui_Expecto_AppVeyor.md index 84afcc4405..98057d669a 100644 --- a/docs/wiz/Windows_Other_Gui_Expecto_AppVeyor.md +++ b/docs/wiz/Windows_Other_Gui_Expecto_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_Expecto_AzureDevOps.md b/docs/wiz/Windows_Other_Gui_Expecto_AzureDevOps.md index 99be4da9af..2682878d4d 100644 --- a/docs/wiz/Windows_Other_Gui_Expecto_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Gui_Expecto_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_Expecto_GitHubActions.md b/docs/wiz/Windows_Other_Gui_Expecto_GitHubActions.md index 1f0bb7dd67..142be6ef4c 100644 --- a/docs/wiz/Windows_Other_Gui_Expecto_GitHubActions.md +++ b/docs/wiz/Windows_Other_Gui_Expecto_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_Expecto_None.md b/docs/wiz/Windows_Other_Gui_Expecto_None.md index 7628c97e62..b034cd2324 100644 --- a/docs/wiz/Windows_Other_Gui_Expecto_None.md +++ b/docs/wiz/Windows_Other_Gui_Expecto_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_Fixie_AppVeyor.md b/docs/wiz/Windows_Other_Gui_Fixie_AppVeyor.md index d6a6805f71..7a4d74aabf 100644 --- a/docs/wiz/Windows_Other_Gui_Fixie_AppVeyor.md +++ b/docs/wiz/Windows_Other_Gui_Fixie_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_Fixie_AzureDevOps.md b/docs/wiz/Windows_Other_Gui_Fixie_AzureDevOps.md index 8117f9db9d..0085cf11a4 100644 --- a/docs/wiz/Windows_Other_Gui_Fixie_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Gui_Fixie_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_Fixie_GitHubActions.md b/docs/wiz/Windows_Other_Gui_Fixie_GitHubActions.md index 2bb27c9ba0..f842982c67 100644 --- a/docs/wiz/Windows_Other_Gui_Fixie_GitHubActions.md +++ b/docs/wiz/Windows_Other_Gui_Fixie_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_Fixie_None.md b/docs/wiz/Windows_Other_Gui_Fixie_None.md index a2f8b992a0..3cc44e37e7 100644 --- a/docs/wiz/Windows_Other_Gui_Fixie_None.md +++ b/docs/wiz/Windows_Other_Gui_Fixie_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_MSTest_AppVeyor.md b/docs/wiz/Windows_Other_Gui_MSTest_AppVeyor.md index 1c3f11116d..68971f92ea 100644 --- a/docs/wiz/Windows_Other_Gui_MSTest_AppVeyor.md +++ b/docs/wiz/Windows_Other_Gui_MSTest_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_MSTest_AzureDevOps.md b/docs/wiz/Windows_Other_Gui_MSTest_AzureDevOps.md index 1ea29ad16b..136ee468af 100644 --- a/docs/wiz/Windows_Other_Gui_MSTest_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Gui_MSTest_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_MSTest_GitHubActions.md b/docs/wiz/Windows_Other_Gui_MSTest_GitHubActions.md index f3fab85814..587015af92 100644 --- a/docs/wiz/Windows_Other_Gui_MSTest_GitHubActions.md +++ b/docs/wiz/Windows_Other_Gui_MSTest_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_MSTest_None.md b/docs/wiz/Windows_Other_Gui_MSTest_None.md index 3d2285bd19..72886e8400 100644 --- a/docs/wiz/Windows_Other_Gui_MSTest_None.md +++ b/docs/wiz/Windows_Other_Gui_MSTest_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_NUnit_AppVeyor.md b/docs/wiz/Windows_Other_Gui_NUnit_AppVeyor.md index 6222aa30bf..746a600f9c 100644 --- a/docs/wiz/Windows_Other_Gui_NUnit_AppVeyor.md +++ b/docs/wiz/Windows_Other_Gui_NUnit_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_NUnit_AzureDevOps.md b/docs/wiz/Windows_Other_Gui_NUnit_AzureDevOps.md index 112e825eba..bce0bd7b03 100644 --- a/docs/wiz/Windows_Other_Gui_NUnit_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Gui_NUnit_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_NUnit_GitHubActions.md b/docs/wiz/Windows_Other_Gui_NUnit_GitHubActions.md index d36178da67..05f9fd356e 100644 --- a/docs/wiz/Windows_Other_Gui_NUnit_GitHubActions.md +++ b/docs/wiz/Windows_Other_Gui_NUnit_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_NUnit_None.md b/docs/wiz/Windows_Other_Gui_NUnit_None.md index 8eb9b1c585..034854c9a9 100644 --- a/docs/wiz/Windows_Other_Gui_NUnit_None.md +++ b/docs/wiz/Windows_Other_Gui_NUnit_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_TUnit_AppVeyor.md b/docs/wiz/Windows_Other_Gui_TUnit_AppVeyor.md index afad7ba9cb..0b00d4a7ea 100644 --- a/docs/wiz/Windows_Other_Gui_TUnit_AppVeyor.md +++ b/docs/wiz/Windows_Other_Gui_TUnit_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_TUnit_AzureDevOps.md b/docs/wiz/Windows_Other_Gui_TUnit_AzureDevOps.md index 59b27d971a..5468eee259 100644 --- a/docs/wiz/Windows_Other_Gui_TUnit_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Gui_TUnit_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_TUnit_GitHubActions.md b/docs/wiz/Windows_Other_Gui_TUnit_GitHubActions.md index 1a5a72979b..e9f6994e0e 100644 --- a/docs/wiz/Windows_Other_Gui_TUnit_GitHubActions.md +++ b/docs/wiz/Windows_Other_Gui_TUnit_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_TUnit_None.md b/docs/wiz/Windows_Other_Gui_TUnit_None.md index 2d71d98e9f..9ba87021ae 100644 --- a/docs/wiz/Windows_Other_Gui_TUnit_None.md +++ b/docs/wiz/Windows_Other_Gui_TUnit_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_XunitV3_AppVeyor.md b/docs/wiz/Windows_Other_Gui_XunitV3_AppVeyor.md index 3d0a1cc486..fbdd4ef7aa 100644 --- a/docs/wiz/Windows_Other_Gui_XunitV3_AppVeyor.md +++ b/docs/wiz/Windows_Other_Gui_XunitV3_AppVeyor.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_XunitV3_AzureDevOps.md b/docs/wiz/Windows_Other_Gui_XunitV3_AzureDevOps.md index fb8a8ed1c7..af7f6da5b2 100644 --- a/docs/wiz/Windows_Other_Gui_XunitV3_AzureDevOps.md +++ b/docs/wiz/Windows_Other_Gui_XunitV3_AzureDevOps.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_XunitV3_GitHubActions.md b/docs/wiz/Windows_Other_Gui_XunitV3_GitHubActions.md index 83c762bc95..845569f509 100644 --- a/docs/wiz/Windows_Other_Gui_XunitV3_GitHubActions.md +++ b/docs/wiz/Windows_Other_Gui_XunitV3_GitHubActions.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Other_Gui_XunitV3_None.md b/docs/wiz/Windows_Other_Gui_XunitV3_None.md index ee4138264c..9c8522e4b6 100644 --- a/docs/wiz/Windows_Other_Gui_XunitV3_None.md +++ b/docs/wiz/Windows_Other_Gui_XunitV3_None.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_Expecto_AppVeyor.md b/docs/wiz/Windows_Rider_Cli_Expecto_AppVeyor.md index 4b16d17ab9..579ae36c8b 100644 --- a/docs/wiz/Windows_Rider_Cli_Expecto_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Cli_Expecto_AppVeyor.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_Expecto_AzureDevOps.md b/docs/wiz/Windows_Rider_Cli_Expecto_AzureDevOps.md index 295c6f6196..16b0ca1f39 100644 --- a/docs/wiz/Windows_Rider_Cli_Expecto_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Cli_Expecto_AzureDevOps.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_Expecto_GitHubActions.md b/docs/wiz/Windows_Rider_Cli_Expecto_GitHubActions.md index d98b7124bb..08b4ef9d86 100644 --- a/docs/wiz/Windows_Rider_Cli_Expecto_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Cli_Expecto_GitHubActions.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_Expecto_None.md b/docs/wiz/Windows_Rider_Cli_Expecto_None.md index f63dfe8b31..74eafaaca5 100644 --- a/docs/wiz/Windows_Rider_Cli_Expecto_None.md +++ b/docs/wiz/Windows_Rider_Cli_Expecto_None.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_Fixie_AppVeyor.md b/docs/wiz/Windows_Rider_Cli_Fixie_AppVeyor.md index 339e5b9133..1f4f9c7f0b 100644 --- a/docs/wiz/Windows_Rider_Cli_Fixie_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Cli_Fixie_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_Fixie_AzureDevOps.md b/docs/wiz/Windows_Rider_Cli_Fixie_AzureDevOps.md index 1efb540552..cc94fba3ff 100644 --- a/docs/wiz/Windows_Rider_Cli_Fixie_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Cli_Fixie_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_Fixie_GitHubActions.md b/docs/wiz/Windows_Rider_Cli_Fixie_GitHubActions.md index b89d3d206d..bc6b87b058 100644 --- a/docs/wiz/Windows_Rider_Cli_Fixie_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Cli_Fixie_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_Fixie_None.md b/docs/wiz/Windows_Rider_Cli_Fixie_None.md index 63e17450fc..86219a99e1 100644 --- a/docs/wiz/Windows_Rider_Cli_Fixie_None.md +++ b/docs/wiz/Windows_Rider_Cli_Fixie_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_MSTest_AppVeyor.md b/docs/wiz/Windows_Rider_Cli_MSTest_AppVeyor.md index 7614ed6ecc..f08396a2b7 100644 --- a/docs/wiz/Windows_Rider_Cli_MSTest_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Cli_MSTest_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_MSTest_AzureDevOps.md b/docs/wiz/Windows_Rider_Cli_MSTest_AzureDevOps.md index aa5c2cbffe..5ec953731b 100644 --- a/docs/wiz/Windows_Rider_Cli_MSTest_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Cli_MSTest_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_MSTest_GitHubActions.md b/docs/wiz/Windows_Rider_Cli_MSTest_GitHubActions.md index 7844db6987..eacb21469e 100644 --- a/docs/wiz/Windows_Rider_Cli_MSTest_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Cli_MSTest_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_MSTest_None.md b/docs/wiz/Windows_Rider_Cli_MSTest_None.md index 732feda40c..bf4f89d1cb 100644 --- a/docs/wiz/Windows_Rider_Cli_MSTest_None.md +++ b/docs/wiz/Windows_Rider_Cli_MSTest_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_NUnit_AppVeyor.md b/docs/wiz/Windows_Rider_Cli_NUnit_AppVeyor.md index 1a6467b32a..c93319ff98 100644 --- a/docs/wiz/Windows_Rider_Cli_NUnit_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Cli_NUnit_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_NUnit_AzureDevOps.md b/docs/wiz/Windows_Rider_Cli_NUnit_AzureDevOps.md index c2688ba07f..1b98515c9a 100644 --- a/docs/wiz/Windows_Rider_Cli_NUnit_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Cli_NUnit_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_NUnit_GitHubActions.md b/docs/wiz/Windows_Rider_Cli_NUnit_GitHubActions.md index faffa7b103..ad2b77a270 100644 --- a/docs/wiz/Windows_Rider_Cli_NUnit_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Cli_NUnit_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_NUnit_None.md b/docs/wiz/Windows_Rider_Cli_NUnit_None.md index 3a0e2e5fd3..0f8d58697e 100644 --- a/docs/wiz/Windows_Rider_Cli_NUnit_None.md +++ b/docs/wiz/Windows_Rider_Cli_NUnit_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_TUnit_AppVeyor.md b/docs/wiz/Windows_Rider_Cli_TUnit_AppVeyor.md index 60c0a2aeb6..68d48a3b9b 100644 --- a/docs/wiz/Windows_Rider_Cli_TUnit_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Cli_TUnit_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_TUnit_AzureDevOps.md b/docs/wiz/Windows_Rider_Cli_TUnit_AzureDevOps.md index d61baa8f11..3171da04e6 100644 --- a/docs/wiz/Windows_Rider_Cli_TUnit_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Cli_TUnit_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_TUnit_GitHubActions.md b/docs/wiz/Windows_Rider_Cli_TUnit_GitHubActions.md index 0b571ede02..70322e67de 100644 --- a/docs/wiz/Windows_Rider_Cli_TUnit_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Cli_TUnit_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_TUnit_None.md b/docs/wiz/Windows_Rider_Cli_TUnit_None.md index 00755dcaea..a6f9dbc72b 100644 --- a/docs/wiz/Windows_Rider_Cli_TUnit_None.md +++ b/docs/wiz/Windows_Rider_Cli_TUnit_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_XunitV3_AppVeyor.md b/docs/wiz/Windows_Rider_Cli_XunitV3_AppVeyor.md index 39921fb13b..0928d8cef6 100644 --- a/docs/wiz/Windows_Rider_Cli_XunitV3_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Cli_XunitV3_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_XunitV3_AzureDevOps.md b/docs/wiz/Windows_Rider_Cli_XunitV3_AzureDevOps.md index 692b455511..6280f465e7 100644 --- a/docs/wiz/Windows_Rider_Cli_XunitV3_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Cli_XunitV3_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_XunitV3_GitHubActions.md b/docs/wiz/Windows_Rider_Cli_XunitV3_GitHubActions.md index 8dd7a71c25..266ef3ba39 100644 --- a/docs/wiz/Windows_Rider_Cli_XunitV3_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Cli_XunitV3_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Cli_XunitV3_None.md b/docs/wiz/Windows_Rider_Cli_XunitV3_None.md index 6cd81636a8..8818e0559a 100644 --- a/docs/wiz/Windows_Rider_Cli_XunitV3_None.md +++ b/docs/wiz/Windows_Rider_Cli_XunitV3_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_Expecto_AppVeyor.md b/docs/wiz/Windows_Rider_Gui_Expecto_AppVeyor.md index 17c03c1c9b..434da6f6d4 100644 --- a/docs/wiz/Windows_Rider_Gui_Expecto_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Gui_Expecto_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_Expecto_AzureDevOps.md b/docs/wiz/Windows_Rider_Gui_Expecto_AzureDevOps.md index c56d506b9e..7a135b6381 100644 --- a/docs/wiz/Windows_Rider_Gui_Expecto_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Gui_Expecto_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_Expecto_GitHubActions.md b/docs/wiz/Windows_Rider_Gui_Expecto_GitHubActions.md index cd3570deba..327d4a1919 100644 --- a/docs/wiz/Windows_Rider_Gui_Expecto_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Gui_Expecto_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_Expecto_None.md b/docs/wiz/Windows_Rider_Gui_Expecto_None.md index ffeaaf51eb..6db69ea2df 100644 --- a/docs/wiz/Windows_Rider_Gui_Expecto_None.md +++ b/docs/wiz/Windows_Rider_Gui_Expecto_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_Fixie_AppVeyor.md b/docs/wiz/Windows_Rider_Gui_Fixie_AppVeyor.md index 85faa38c02..71bc7803ab 100644 --- a/docs/wiz/Windows_Rider_Gui_Fixie_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Gui_Fixie_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_Fixie_AzureDevOps.md b/docs/wiz/Windows_Rider_Gui_Fixie_AzureDevOps.md index 299272ee2e..31de7b59b8 100644 --- a/docs/wiz/Windows_Rider_Gui_Fixie_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Gui_Fixie_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_Fixie_GitHubActions.md b/docs/wiz/Windows_Rider_Gui_Fixie_GitHubActions.md index 443915a584..c9827e84fb 100644 --- a/docs/wiz/Windows_Rider_Gui_Fixie_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Gui_Fixie_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_Fixie_None.md b/docs/wiz/Windows_Rider_Gui_Fixie_None.md index 5aa340f518..a6d99ba292 100644 --- a/docs/wiz/Windows_Rider_Gui_Fixie_None.md +++ b/docs/wiz/Windows_Rider_Gui_Fixie_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_MSTest_AppVeyor.md b/docs/wiz/Windows_Rider_Gui_MSTest_AppVeyor.md index b54ab643c5..671aa8f89b 100644 --- a/docs/wiz/Windows_Rider_Gui_MSTest_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Gui_MSTest_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_MSTest_AzureDevOps.md b/docs/wiz/Windows_Rider_Gui_MSTest_AzureDevOps.md index 9d07a401e9..b67ce69eab 100644 --- a/docs/wiz/Windows_Rider_Gui_MSTest_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Gui_MSTest_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_MSTest_GitHubActions.md b/docs/wiz/Windows_Rider_Gui_MSTest_GitHubActions.md index 0b688a40c3..42f94b0e65 100644 --- a/docs/wiz/Windows_Rider_Gui_MSTest_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Gui_MSTest_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_MSTest_None.md b/docs/wiz/Windows_Rider_Gui_MSTest_None.md index 94a8190c76..2803e7059b 100644 --- a/docs/wiz/Windows_Rider_Gui_MSTest_None.md +++ b/docs/wiz/Windows_Rider_Gui_MSTest_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_NUnit_AppVeyor.md b/docs/wiz/Windows_Rider_Gui_NUnit_AppVeyor.md index ea7e0783b3..1f363a0bcb 100644 --- a/docs/wiz/Windows_Rider_Gui_NUnit_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Gui_NUnit_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_NUnit_AzureDevOps.md b/docs/wiz/Windows_Rider_Gui_NUnit_AzureDevOps.md index 15dceb51db..17f5d040da 100644 --- a/docs/wiz/Windows_Rider_Gui_NUnit_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Gui_NUnit_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_NUnit_GitHubActions.md b/docs/wiz/Windows_Rider_Gui_NUnit_GitHubActions.md index f111f11e93..bf355457f8 100644 --- a/docs/wiz/Windows_Rider_Gui_NUnit_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Gui_NUnit_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_NUnit_None.md b/docs/wiz/Windows_Rider_Gui_NUnit_None.md index 4ebc3f5ac7..5e8811cad7 100644 --- a/docs/wiz/Windows_Rider_Gui_NUnit_None.md +++ b/docs/wiz/Windows_Rider_Gui_NUnit_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_TUnit_AppVeyor.md b/docs/wiz/Windows_Rider_Gui_TUnit_AppVeyor.md index 7dcb097c28..9bc8f9d3aa 100644 --- a/docs/wiz/Windows_Rider_Gui_TUnit_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Gui_TUnit_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_TUnit_AzureDevOps.md b/docs/wiz/Windows_Rider_Gui_TUnit_AzureDevOps.md index 8334ef4b66..26dfc89520 100644 --- a/docs/wiz/Windows_Rider_Gui_TUnit_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Gui_TUnit_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_TUnit_GitHubActions.md b/docs/wiz/Windows_Rider_Gui_TUnit_GitHubActions.md index 885961fd2a..576ec8f2b8 100644 --- a/docs/wiz/Windows_Rider_Gui_TUnit_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Gui_TUnit_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_TUnit_None.md b/docs/wiz/Windows_Rider_Gui_TUnit_None.md index b846174c5f..94b0a166f2 100644 --- a/docs/wiz/Windows_Rider_Gui_TUnit_None.md +++ b/docs/wiz/Windows_Rider_Gui_TUnit_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_XunitV3_AppVeyor.md b/docs/wiz/Windows_Rider_Gui_XunitV3_AppVeyor.md index ed547e4682..99a9858ecf 100644 --- a/docs/wiz/Windows_Rider_Gui_XunitV3_AppVeyor.md +++ b/docs/wiz/Windows_Rider_Gui_XunitV3_AppVeyor.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_XunitV3_AzureDevOps.md b/docs/wiz/Windows_Rider_Gui_XunitV3_AzureDevOps.md index b40616f216..400235312b 100644 --- a/docs/wiz/Windows_Rider_Gui_XunitV3_AzureDevOps.md +++ b/docs/wiz/Windows_Rider_Gui_XunitV3_AzureDevOps.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_XunitV3_GitHubActions.md b/docs/wiz/Windows_Rider_Gui_XunitV3_GitHubActions.md index 81e6249a04..8a200db0d4 100644 --- a/docs/wiz/Windows_Rider_Gui_XunitV3_GitHubActions.md +++ b/docs/wiz/Windows_Rider_Gui_XunitV3_GitHubActions.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_Rider_Gui_XunitV3_None.md b/docs/wiz/Windows_Rider_Gui_XunitV3_None.md index 012edce42d..88a6183617 100644 --- a/docs/wiz/Windows_Rider_Gui_XunitV3_None.md +++ b/docs/wiz/Windows_Rider_Gui_XunitV3_None.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_AppVeyor.md index 5664f0882f..1089c59345 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_AppVeyor.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_AzureDevOps.md index b038c2c7a9..2bf77fb610 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_AzureDevOps.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_GitHubActions.md index a17b193127..cd29f37366 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_GitHubActions.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_None.md index a7904ba166..1693d6e2ae 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Expecto_None.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_AppVeyor.md index 1e508d2c49..0804f216c3 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_AzureDevOps.md index 373380eee0..3e53db18c4 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_GitHubActions.md index 1896cf0a0d..9379bc5e3b 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_None.md index 72e104c724..21e125e679 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_Fixie_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_AppVeyor.md index 2c03649213..5687b153fa 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_AzureDevOps.md index c78abb6f5b..a95525fae3 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_GitHubActions.md index e9bd7ddca7..a587fd10cf 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_None.md index cdb436f135..5c5fd54780 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_MSTest_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_AppVeyor.md index d89743f584..704cd20b1e 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_AzureDevOps.md index 9659366f99..7749daa2bb 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_GitHubActions.md index 1c1bf53ffd..6710cca292 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_None.md index b3fdce1c9c..c624d3e636 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_NUnit_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_AppVeyor.md index d865d46afa..4630042f83 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_AzureDevOps.md index 6df918637e..d4c82454d8 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_GitHubActions.md index ba1cb84505..405ee032f0 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_None.md index 6bc0975637..af425e18a1 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_TUnit_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_AppVeyor.md index b4c396a7de..93002ca350 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_AzureDevOps.md index c590489881..86b147356f 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_GitHubActions.md index b10e407e5c..66eab7d239 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_None.md index babfdffd57..6701c274b9 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Cli_XunitV3_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_AppVeyor.md index 31af604099..355fec2a63 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_AzureDevOps.md index 1d33b6bd14..11a43f47de 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_GitHubActions.md index c5f519a527..77b9e1b01d 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_None.md index 9b13810808..ccd488f308 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Expecto_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_AppVeyor.md index 7174718d9d..d56aafca90 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_AzureDevOps.md index 3d3ac54cfe..7917c10027 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_GitHubActions.md index c8de2c6a64..ceecdc6226 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_None.md index 39cc10880a..002b24149f 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_Fixie_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_AppVeyor.md index 91bf58edee..8a68c281d1 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_AzureDevOps.md index 5e06ee0fd6..0f76175eb2 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_GitHubActions.md index f4f5243d1a..677fc308c2 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_None.md index 7dcc7ee665..5171add4a9 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_MSTest_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_AppVeyor.md index a2be7c011d..556246650a 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_AzureDevOps.md index 7f6ad20229..e480b92ff3 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_GitHubActions.md index 8723e1ea88..1ade42cb87 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_None.md index 41c4351903..74c4a01d56 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_NUnit_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_AppVeyor.md index 62cfd39c05..dd31ceda33 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_AzureDevOps.md index 4d5eb73666..2f0e3d0c39 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_GitHubActions.md index ad8ce9c42f..f586b3a20f 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_None.md index fe9e9c94d9..ecea0f818f 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_TUnit_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_AppVeyor.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_AppVeyor.md index fd7dc776a7..95beecf7d2 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_AppVeyor.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_AzureDevOps.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_AzureDevOps.md index f3cd45c534..d5be877d4b 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_AzureDevOps.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_GitHubActions.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_GitHubActions.md index 33e0fe1308..12bd34b32b 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_GitHubActions.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_None.md b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_None.md index 49ab4be5de..95c8f21c6c 100644 --- a/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_None.md +++ b/docs/wiz/Windows_VisualStudioWithReSharper_Gui_XunitV3_None.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_Expecto_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Cli_Expecto_AppVeyor.md index 4609680eb7..cffd6888ee 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_Expecto_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Cli_Expecto_AppVeyor.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_Expecto_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Cli_Expecto_AzureDevOps.md index 2852349c3c..3a30f7da1a 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_Expecto_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Cli_Expecto_AzureDevOps.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_Expecto_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Cli_Expecto_GitHubActions.md index 9026f7a3a7..ed2f98be1b 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_Expecto_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Cli_Expecto_GitHubActions.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_Expecto_None.md b/docs/wiz/Windows_VisualStudio_Cli_Expecto_None.md index 239cd40454..aae0529169 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_Expecto_None.md +++ b/docs/wiz/Windows_VisualStudio_Cli_Expecto_None.md @@ -134,7 +134,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_Fixie_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Cli_Fixie_AppVeyor.md index b8eddeb57f..2fa7d139d1 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_Fixie_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Cli_Fixie_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_Fixie_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Cli_Fixie_AzureDevOps.md index 4c259ff3a8..3f0139e3f7 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_Fixie_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Cli_Fixie_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_Fixie_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Cli_Fixie_GitHubActions.md index 6aaa20465d..79f6d8e3e4 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_Fixie_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Cli_Fixie_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_Fixie_None.md b/docs/wiz/Windows_VisualStudio_Cli_Fixie_None.md index 0c19debdd1..8e8b12a478 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_Fixie_None.md +++ b/docs/wiz/Windows_VisualStudio_Cli_Fixie_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_MSTest_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Cli_MSTest_AppVeyor.md index e03eaedf8d..84144f1b87 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_MSTest_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Cli_MSTest_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_MSTest_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Cli_MSTest_AzureDevOps.md index 69e95f6131..773a232d96 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_MSTest_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Cli_MSTest_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_MSTest_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Cli_MSTest_GitHubActions.md index 4e1c087f25..703e33d062 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_MSTest_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Cli_MSTest_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_MSTest_None.md b/docs/wiz/Windows_VisualStudio_Cli_MSTest_None.md index c7ab6ff2bc..8834eea0b2 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_MSTest_None.md +++ b/docs/wiz/Windows_VisualStudio_Cli_MSTest_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_NUnit_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Cli_NUnit_AppVeyor.md index d49beb0141..f41786a683 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_NUnit_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Cli_NUnit_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_NUnit_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Cli_NUnit_AzureDevOps.md index 4b160e5bcf..0bab6a060f 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_NUnit_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Cli_NUnit_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_NUnit_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Cli_NUnit_GitHubActions.md index 864b79d96b..ffdac735d7 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_NUnit_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Cli_NUnit_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_NUnit_None.md b/docs/wiz/Windows_VisualStudio_Cli_NUnit_None.md index 8e7f27e250..e78027abf8 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_NUnit_None.md +++ b/docs/wiz/Windows_VisualStudio_Cli_NUnit_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_TUnit_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Cli_TUnit_AppVeyor.md index d829cb940b..a021a6ec80 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_TUnit_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Cli_TUnit_AppVeyor.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_TUnit_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Cli_TUnit_AzureDevOps.md index 1652126a0a..4c819da706 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_TUnit_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Cli_TUnit_AzureDevOps.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_TUnit_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Cli_TUnit_GitHubActions.md index 7276aa247b..4bc362e7ae 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_TUnit_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Cli_TUnit_GitHubActions.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_TUnit_None.md b/docs/wiz/Windows_VisualStudio_Cli_TUnit_None.md index a96f89821f..1faf8dc134 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_TUnit_None.md +++ b/docs/wiz/Windows_VisualStudio_Cli_TUnit_None.md @@ -133,7 +133,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_XunitV3_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Cli_XunitV3_AppVeyor.md index a5778e8f8f..2291e8448c 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_XunitV3_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Cli_XunitV3_AppVeyor.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_XunitV3_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Cli_XunitV3_AzureDevOps.md index d2d37c5e3d..5d5f250193 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_XunitV3_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Cli_XunitV3_AzureDevOps.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_XunitV3_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Cli_XunitV3_GitHubActions.md index 81e3aa4918..c6843bc1c5 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_XunitV3_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Cli_XunitV3_GitHubActions.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Cli_XunitV3_None.md b/docs/wiz/Windows_VisualStudio_Cli_XunitV3_None.md index 728d516ba7..05d4418db2 100644 --- a/docs/wiz/Windows_VisualStudio_Cli_XunitV3_None.md +++ b/docs/wiz/Windows_VisualStudio_Cli_XunitV3_None.md @@ -135,7 +135,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_Expecto_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Gui_Expecto_AppVeyor.md index 7c1e83e527..6dae4a182a 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_Expecto_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Gui_Expecto_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_Expecto_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Gui_Expecto_AzureDevOps.md index 6d8d9b2957..0da7816a52 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_Expecto_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Gui_Expecto_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_Expecto_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Gui_Expecto_GitHubActions.md index 16e510c675..172ec2aae3 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_Expecto_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Gui_Expecto_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_Expecto_None.md b/docs/wiz/Windows_VisualStudio_Gui_Expecto_None.md index 1ef502edf3..d0aca940a4 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_Expecto_None.md +++ b/docs/wiz/Windows_VisualStudio_Gui_Expecto_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_Fixie_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Gui_Fixie_AppVeyor.md index 044abb3642..048f947900 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_Fixie_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Gui_Fixie_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_Fixie_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Gui_Fixie_AzureDevOps.md index ef99a53903..eff4965bf1 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_Fixie_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Gui_Fixie_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_Fixie_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Gui_Fixie_GitHubActions.md index 7b431d0a86..f68cc5e7c5 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_Fixie_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Gui_Fixie_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_Fixie_None.md b/docs/wiz/Windows_VisualStudio_Gui_Fixie_None.md index 9c794f35aa..cb98cb8cdf 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_Fixie_None.md +++ b/docs/wiz/Windows_VisualStudio_Gui_Fixie_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_MSTest_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Gui_MSTest_AppVeyor.md index 92babf2f58..81a8e0dfbf 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_MSTest_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Gui_MSTest_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_MSTest_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Gui_MSTest_AzureDevOps.md index e19be2628b..5ee2c46dfb 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_MSTest_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Gui_MSTest_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_MSTest_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Gui_MSTest_GitHubActions.md index 6ff666ea1a..ae96991c74 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_MSTest_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Gui_MSTest_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_MSTest_None.md b/docs/wiz/Windows_VisualStudio_Gui_MSTest_None.md index fa4b024a71..89fce39781 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_MSTest_None.md +++ b/docs/wiz/Windows_VisualStudio_Gui_MSTest_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_NUnit_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Gui_NUnit_AppVeyor.md index 068405059a..f5ffa010a6 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_NUnit_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Gui_NUnit_AppVeyor.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_NUnit_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Gui_NUnit_AzureDevOps.md index 869d90a3d8..115b2aee76 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_NUnit_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Gui_NUnit_AzureDevOps.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_NUnit_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Gui_NUnit_GitHubActions.md index 57ecc86fe5..b63f6c2f98 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_NUnit_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Gui_NUnit_GitHubActions.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_NUnit_None.md b/docs/wiz/Windows_VisualStudio_Gui_NUnit_None.md index 8269df47b7..734e5052a5 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_NUnit_None.md +++ b/docs/wiz/Windows_VisualStudio_Gui_NUnit_None.md @@ -141,7 +141,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_TUnit_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Gui_TUnit_AppVeyor.md index 2d8f6d2363..4dfe469eeb 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_TUnit_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Gui_TUnit_AppVeyor.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_TUnit_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Gui_TUnit_AzureDevOps.md index 72ede708ba..d2c71b24d3 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_TUnit_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Gui_TUnit_AzureDevOps.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_TUnit_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Gui_TUnit_GitHubActions.md index 2c36188304..0ba6a96555 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_TUnit_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Gui_TUnit_GitHubActions.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_TUnit_None.md b/docs/wiz/Windows_VisualStudio_Gui_TUnit_None.md index b91d5e5b06..a3d392f4cc 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_TUnit_None.md +++ b/docs/wiz/Windows_VisualStudio_Gui_TUnit_None.md @@ -139,7 +139,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_XunitV3_AppVeyor.md b/docs/wiz/Windows_VisualStudio_Gui_XunitV3_AppVeyor.md index d9a5e5c91e..3832d6f85d 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_XunitV3_AppVeyor.md +++ b/docs/wiz/Windows_VisualStudio_Gui_XunitV3_AppVeyor.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_XunitV3_AzureDevOps.md b/docs/wiz/Windows_VisualStudio_Gui_XunitV3_AzureDevOps.md index eb2be56256..33d35db478 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_XunitV3_AzureDevOps.md +++ b/docs/wiz/Windows_VisualStudio_Gui_XunitV3_AzureDevOps.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_XunitV3_GitHubActions.md b/docs/wiz/Windows_VisualStudio_Gui_XunitV3_GitHubActions.md index 9515cd81e7..84873e4017 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_XunitV3_GitHubActions.md +++ b/docs/wiz/Windows_VisualStudio_Gui_XunitV3_GitHubActions.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/docs/wiz/Windows_VisualStudio_Gui_XunitV3_None.md b/docs/wiz/Windows_VisualStudio_Gui_XunitV3_None.md index 116da99b40..8de32dda8b 100644 --- a/docs/wiz/Windows_VisualStudio_Gui_XunitV3_None.md +++ b/docs/wiz/Windows_VisualStudio_Gui_XunitV3_None.md @@ -140,7 +140,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check diff --git a/readme.md b/readme.md index bd6f7a9625..9006a0771a 100644 --- a/readme.md +++ b/readme.md @@ -677,7 +677,12 @@ indent_style = space **Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.** -**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. +**Visual Studio Code** does not apply the EditorConfig `end_of_line` setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with `crlf` on Windows, taken from the default `files.eol`. Verify then rejects that file for containing a carriage return. Installing the [EditorConfig for VS Code extension](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) applies `end_of_line = lf` on save. Setting `"files.eol": "\n"` in Visual Studio Code settings has the same effect without the extension. + + +#### Newline tolerance + +The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See [Newline tolerance](/docs/newline-tolerance.md). ### Conventions check @@ -1095,6 +1100,7 @@ Browser testing via * [Custom Diff Tool](https://github.com/VerifyTests/DiffEngine/blob/master/docs/diff-tool.custom.md) * [Using anonymous types](/docs/anonymous-types.md) * [Verifying binary data](/docs/binary.md) + * [Newline tolerance](/docs/newline-tolerance.md) * [Exception Message Format](/docs/exception-message-format.md) * [Build server](/docs/build-server.md) * [Kill process locking file](/docs/kill-process-locking-file.md) diff --git a/src/ModuleInitDocs/FixNewlinesOnRead.cs b/src/ModuleInitDocs/FixNewlinesOnRead.cs new file mode 100644 index 0000000000..9e2b70ad47 --- /dev/null +++ b/src/ModuleInitDocs/FixNewlinesOnRead.cs @@ -0,0 +1,13 @@ +public class FixNewlinesOnRead +{ + #region FixNewlinesOnRead + + public static class ModuleInitializer + { + [ModuleInitializer] + public static void Init() => + VerifierSettings.FixNewlinesOnRead(); + } + + #endregion +} diff --git a/src/ModuleInitDocs/IgnoreTrailingNewline.cs b/src/ModuleInitDocs/IgnoreTrailingNewline.cs new file mode 100644 index 0000000000..e59b1aafe1 --- /dev/null +++ b/src/ModuleInitDocs/IgnoreTrailingNewline.cs @@ -0,0 +1,13 @@ +public class IgnoreTrailingNewline +{ + #region IgnoreTrailingNewline + + public static class ModuleInitializer + { + [ModuleInitializer] + public static void Init() => + VerifierSettings.IgnoreTrailingNewline(); + } + + #endregion +} diff --git a/src/StaticSettingsTests/FixNewlinesOnReadTests.cs b/src/StaticSettingsTests/FixNewlinesOnReadTests.cs new file mode 100644 index 0000000000..680e30e7b0 --- /dev/null +++ b/src/StaticSettingsTests/FixNewlinesOnReadTests.cs @@ -0,0 +1,84 @@ +// Lives here, rather than in Verify.Tests, since FixNewlinesOnRead is a static setting, and this +// project runs serially with BaseTest resetting it between tests. +public class FixNewlinesOnReadTests : + BaseTest +{ + [Fact] + public async Task RejectedByDefault() + { + using var temp = new TempDirectory(); + await File.WriteAllTextAsync(VerifiedPath(temp), "a\r\nb"); + + var exception = await Assert.ThrowsAnyAsync(() => Verify("a\nb", Settings(temp))); + + Assert.Contains("carriage return", exception.Message); + } + + [Fact] + public async Task Crlf() + { + VerifierSettings.FixNewlinesOnRead(); + + using var temp = new TempDirectory(); + await File.WriteAllTextAsync(VerifiedPath(temp), "a\r\nb"); + + await Verify("a\nb", Settings(temp)); + } + + [Fact] + public async Task Cr() + { + VerifierSettings.FixNewlinesOnRead(); + + using var temp = new TempDirectory(); + await File.WriteAllTextAsync(VerifiedPath(temp), "a\rb"); + + await Verify("a\nb", Settings(temp)); + } + + [Fact] + public async Task VerifiedIsNotRewritten() + { + VerifierSettings.FixNewlinesOnRead(); + + using var temp = new TempDirectory(); + var verified = VerifiedPath(temp); + await File.WriteAllTextAsync(verified, "a\r\nb"); + + await Verify("a\nb", Settings(temp)); + + // Normalizing happens in memory. A passing test does not write, so the file on disk + // keeps its line endings. + Assert.Equal("a\r\nb", await File.ReadAllTextAsync(verified)); + } + + [Fact] + public async Task MismatchStillFails() + { + VerifierSettings.FixNewlinesOnRead(); + + using var temp = new TempDirectory(); + await File.WriteAllTextAsync(VerifiedPath(temp), "a\r\nb"); + + // Line endings are normalized, the rest of the content is still compared as is + var exception = await Assert.ThrowsAsync(() => Verify("a\nc", Settings(temp))); + + Assert.DoesNotContain("carriage return", exception.Message); + Assert.Equal("a\nc", await File.ReadAllTextAsync(ReceivedPath(temp))); + } + + static VerifySettings Settings(TempDirectory temp) + { + var settings = new VerifySettings(); + settings.UseDirectory(temp); + // Several verifies below are expected to fail, so without this the diff tool is launched + settings.DisableDiff(); + return settings; + } + + static string VerifiedPath(TempDirectory temp, [CallerMemberName] string name = "") => + temp.BuildPath($"{nameof(FixNewlinesOnReadTests)}.{name}.verified.txt"); + + static string ReceivedPath(TempDirectory temp, [CallerMemberName] string name = "") => + temp.BuildPath($"{nameof(FixNewlinesOnReadTests)}.{name}.received.txt"); +} diff --git a/src/StaticSettingsTests/IgnoreTrailingNewlineTests.cs b/src/StaticSettingsTests/IgnoreTrailingNewlineTests.cs new file mode 100644 index 0000000000..8a66dbadc2 --- /dev/null +++ b/src/StaticSettingsTests/IgnoreTrailingNewlineTests.cs @@ -0,0 +1,99 @@ +// Lives here, rather than in Verify.Tests, since IgnoreTrailingNewline is a static setting, and +// this project runs serially with BaseTest resetting it between tests. +public class IgnoreTrailingNewlineTests : + BaseTest +{ + [Fact] + public async Task NotIgnoredByDefault() + { + using var temp = new TempDirectory(); + await File.WriteAllTextAsync(VerifiedPath(temp), "a\n"); + + await Assert.ThrowsAsync(() => Verify("a", Settings(temp))); + } + + [Fact] + public async Task Ignored() + { + VerifierSettings.IgnoreTrailingNewline(); + + using var temp = new TempDirectory(); + await File.WriteAllTextAsync(VerifiedPath(temp), "a\n"); + + await Verify("a", Settings(temp)); + } + + [Fact] + public async Task IgnoredWhenReceivedAlsoEndsInNewline() + { + VerifierSettings.IgnoreTrailingNewline(); + + using var temp = new TempDirectory(); + await File.WriteAllTextAsync(VerifiedPath(temp), "a\n\n"); + + await Verify("a\n", Settings(temp)); + } + + [Fact] + public async Task OnlyASingleNewline() + { + VerifierSettings.IgnoreTrailingNewline(); + + using var temp = new TempDirectory(); + await File.WriteAllTextAsync(VerifiedPath(temp), "a\n\n"); + + await Assert.ThrowsAsync(() => Verify("a", Settings(temp))); + } + + [Fact] + public async Task OnlyWhereTheNewlineIsTheSoleDifference() + { + VerifierSettings.IgnoreTrailingNewline(); + + using var temp = new TempDirectory(); + await File.WriteAllTextAsync(VerifiedPath(temp), "b\n"); + + await Assert.ThrowsAsync(() => Verify("a", Settings(temp))); + } + + [Fact] + public async Task OnlyForVerified() + { + VerifierSettings.IgnoreTrailingNewline(); + + using var temp = new TempDirectory(); + await File.WriteAllTextAsync(VerifiedPath(temp), "a"); + + // The tolerance exists for editors adding a final newline to verified. Received is + // written by Verify, so a trailing newline there is part of what the test produced. + await Assert.ThrowsAsync(() => Verify("a\n", Settings(temp))); + } + + [Fact] + public async Task VerifiedIsNotRewritten() + { + VerifierSettings.IgnoreTrailingNewline(); + + using var temp = new TempDirectory(); + var verified = VerifiedPath(temp); + await File.WriteAllTextAsync(verified, "a\n"); + + await Verify("a", Settings(temp)); + + // Trimming happens in memory. A passing test does not write, so the trailing newline + // stays on disk. + Assert.Equal("a\n", await File.ReadAllTextAsync(verified)); + } + + static VerifySettings Settings(TempDirectory temp) + { + var settings = new VerifySettings(); + settings.UseDirectory(temp); + // Several verifies above are expected to fail, so without this the diff tool is launched + settings.DisableDiff(); + return settings; + } + + static string VerifiedPath(TempDirectory temp, [CallerMemberName] string name = "") => + temp.BuildPath($"{nameof(IgnoreTrailingNewlineTests)}.{name}.verified.txt"); +} diff --git a/src/Verify/Compare/Comparer.cs b/src/Verify/Compare/Comparer.cs index e265e3b4be..6f73471445 100644 --- a/src/Verify/Compare/Comparer.cs +++ b/src/Verify/Compare/Comparer.cs @@ -14,11 +14,18 @@ public static async Task Text(FilePair filePair, StringBuilder r var verified = await File.ReadAllTextAsync(filePair.VerifiedPath, VerifierSettings.Encoding); if (verified.Contains('\r')) { - // Write received before throwing. Otherwise the run produces no output at all, - // which reads as "verify silently did nothing" rather than a line ending problem. - // Accepting the received file also rewrites verified with \n endings. - IoHelpers.WriteText(filePair.ReceivedPath, received); - throw new VerifiedLineEndingException(filePair.VerifiedPath, filePair.Extension); + if (!VerifierSettings.fixNewlinesOnRead) + { + // Write received before throwing. Otherwise the run produces no output at all, + // which reads as "verify silently did nothing" rather than a line ending problem. + // Accepting the received file also rewrites verified with \n endings. + IoHelpers.WriteText(filePair.ReceivedPath, received); + throw new VerifiedLineEndingException(filePair.VerifiedPath, filePair.Extension); + } + + verified = verified + .Replace("\r\n", "\n") + .Replace('\r', '\n'); } var result = await CompareStrings(filePair.Extension, received, verified, settings, bypassComparer); @@ -33,6 +40,15 @@ public static async Task Text(FilePair filePair, StringBuilder r static Task CompareStrings(string extension, StringBuilder received, string verified, VerifySettings settings, bool bypassComparer) { + // Only a single trailing \n, and only where it is the sole difference in length. An + // editor adding a final newline to verified is tolerated, a genuine content change is not. + if (VerifierSettings.ignoreTrailingNewline && + verified.Length - 1 == received.Length && + verified[^1] == '\n') + { + verified = verified[..^1]; + } + var isEqual = received.Equals(verified.AsSpan()); if (!isEqual && !bypassComparer && diff --git a/src/Verify/Compare/VerifiedLineEndingException.cs b/src/Verify/Compare/VerifiedLineEndingException.cs index 24c1192b53..48b4f949c4 100644 --- a/src/Verify/Compare/VerifiedLineEndingException.cs +++ b/src/Verify/Compare/VerifiedLineEndingException.cs @@ -9,4 +9,7 @@ class VerifiedLineEndingException(string path, string extension) : git rm --cached -r . git reset --hard See https://github.com/verifytests/verify#text-file-settings + Alternatively Verify can be made tolerant of line endings in verified files, with + the side effects described in + https://github.com/VerifyTests/Verify/blob/main/docs/newline-tolerance.md """); diff --git a/src/Verify/Serialization/VerifierSettings.cs b/src/Verify/Serialization/VerifierSettings.cs index ae9799c20a..e856d073d5 100644 --- a/src/Verify/Serialization/VerifierSettings.cs +++ b/src/Verify/Serialization/VerifierSettings.cs @@ -163,6 +163,8 @@ internal static void Reset() UniquePrefixDisabled = false; UseUniqueDirectorySplitMode = false; omitContentFromException = false; + fixNewlinesOnRead = false; + ignoreTrailingNewline = false; encoding = new UTF8Encoding(true, true); addAttachments = true; excludedTargets = null; diff --git a/src/Verify/VerifierSettings.cs b/src/Verify/VerifierSettings.cs index 25bd591e8b..0466249abf 100644 --- a/src/Verify/VerifierSettings.cs +++ b/src/Verify/VerifierSettings.cs @@ -33,6 +33,33 @@ public static void AutoVerify(GlobalAutoVerify autoVerify, bool includeBuildServ internal static GlobalAutoVerify? autoVerify; internal static bool throwException; + internal static bool fixNewlinesOnRead; + + /// + /// Normalize `\r\n` and `\r` to `\n` when reading verified files, instead of rejecting a + /// verified file that contains a carriage return. + /// Has side effects. See https://github.com/VerifyTests/Verify/blob/main/docs/newline-tolerance.md + /// + public static void FixNewlinesOnRead() + { + InnerVerifier.ThrowIfVerifyHasBeenRun(); + fixNewlinesOnRead = true; + } + + internal static bool ignoreTrailingNewline; + + /// + /// Treat a verified file that has a single trailing `\n`, where that newline is the only + /// difference, as equal to the received content. + /// Has side effects, and can mask a real change in trailing newlines. See + /// https://github.com/VerifyTests/Verify/blob/main/docs/newline-tolerance.md + /// + public static void IgnoreTrailingNewline() + { + InnerVerifier.ThrowIfVerifyHasBeenRun(); + ignoreTrailingNewline = true; + } + public static void UseUtf8NoBom() => Encoding = new UTF8Encoding(false, true);