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
When the --check option is used, the output only contains if a file was not formatted. It doesn't contain any indication of what part of the file wasn't formatted.
Theoretically you can just run csharpier on the file, but in the case where the --check appears to be a false positive, not having a message means it is harder to track down why it failed.
The text was updated successfully, but these errors were encountered:
I can reproduce this by downloading the zip of the repo and running --check against that. That means I should be able to use the debug version to step through what is going on.
It appears that SyntaxNodeComparerTests formats differently based on if it has \r\n or \n as line endings. So line endings must be included somehow in the width of strings.
When the --check option is used, the output only contains if a file was not formatted. It doesn't contain any indication of what part of the file wasn't formatted.
Theoretically you can just run csharpier on the file, but in the case where the --check appears to be a false positive, not having a message means it is harder to track down why it failed.
The text was updated successfully, but these errors were encountered: