You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different whitespace errors are reported by --verify-no-changes when using indent_style = tab.
I expected --verify-no-changes to report exactly the same errors that would have been fixed if this option were omitted.
This issue seems to be related to the presence of comments in the file.
There is one whitespace error included on line 13.
Run dotnet format whitespace --folder . -v d --verify-no-changes
See it report five whitespace errors (one for line 13 plus two more for each comment in the file)
Remove one of the comments and repeat the above command, see it report three whitespace errors.
Run dotnet format whitespace --folder . -v d
See it fix one whitespace error as expected.
coavins
changed the title
Different whitespace errors reported by --verify-no-changes when using indent_style = tab
[dotnet format] Different whitespace errors reported by --verify-no-changes when using indent_style = tab
Aug 29, 2024
Describe the bug
Different whitespace errors are reported by
--verify-no-changes
when usingindent_style = tab
.I expected
--verify-no-changes
to report exactly the same errors that would have been fixed if this option were omitted.This issue seems to be related to the presence of comments in the file.
See also: dotnet/format#2045
To Reproduce
Put the following source file and .editorconfig into a new folder:
https://gist.github.com/coavins/7734bfd8d661910144b36122b092fe30
There is one whitespace error included on line 13.
Run
dotnet format whitespace --folder . -v d --verify-no-changes
See it report five whitespace errors (one for line 13 plus two more for each comment in the file)
Remove one of the comments and repeat the above command, see it report three whitespace errors.
Run
dotnet format whitespace --folder . -v d
See it fix one whitespace error as expected.
Further technical details
dotnet --info
The text was updated successfully, but these errors were encountered: