[BUG] nx lint fails on dotnet project

[dasco144]

Describe the bug
The nx lint command fails on the dotnet project due to the check argument being removed in favour of verify-no-changes here

To Reproduce

1. run nx lint on your dotnet project
2. the command runs and installs dotnet-format (latest version at time of writing 5.1.225507)
3. the command fails
4. See error

Expected behavior
The command should run and not fail

Screenshots

Environment:

• OS: Windows 10
• Browser: N/A
• Version: 1.4.2
• Affected Packages: nx-dotnet

Additional context
When manually running the same command with check replaced with verify-no-changes, it works as expected

[AgentEnder]

Yikes, I didn't expect that option to change. That seems like a breaking change for no good reason on the dotnet side of things. I'll work on this at some point, need to make sure it works with the older versions too.

Thanks for the report.

[bcallaghan-et]

@dasco144 What version of the .NET SDK are you using? I'm using SDK 5.0.402. Using both dotnet-format 5.1.225507 and 5.1.250801, I see the --check flag rather than the --verify-no-changes flag.

$ dotnet format --version
5.1.250801+4a851ea9707f87d381166c2fc2b2d4b58a10a222

$ dotnet format --help
dotnet-format
  dotnet-format

Usage:
  dotnet-format [options] [<workspace>]

Arguments:
  <workspace>  A path to a solution file, a project file, or a folder containing a solution or project file. If a path is not specified then the current directory is used. [default: ]

Options:
  --no-restore                                                             Doesn't execute an implicit restore before formatting.
  -f, --folder                                                             Whether to treat the `<workspace>` argument as a simple folder of files.
  -w, --fix-whitespace                                                     Run whitespace formatting. Run by default when not applying fixes.
  -s, --fix-style <error|info|warn>                                        Run code style analyzers and apply fixes.
  -a, --fix-analyzers <error|info|warn>                                    Run 3rd party analyzers and apply fixes.
  --diagnostics <diagnostics>                                              A space separated list of diagnostic ids to use as a filter when fixing code style or 3rd party issues. [default: ]
  --include <include>                                                      A list of relative file or folder paths to include in formatting. All files are formatted if empty. [default: ]
  --exclude <exclude>                                                      A list of relative file or folder paths to exclude from formatting. [default: ]
  --check                                                                  Formats files without saving changes to disk. Terminates with a non-zero exit code if any files were formatted.
  --report <report-path>                                                   Accepts a file path, which if provided, will produce a json report in the given directory.
  -v, --verbosity <d|detailed|diag|diagnostic|m|minimal|n|normal|q|quiet>  Set the verbosity level. Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic]
  --binarylog <binary-log-path>                                            Log all project or solution load information to a binary log file.
  --version                                                                Show version information
  -?, -h, --help                                                           Show help and usage information

Similarly, using the --check flag worked with both versions, while using --verify-no-changes resulted in an error.

[dasco144]

Yes I think it is related to the dotnet 6 preview. I installed the Visual Studio 2022 preview and it installed the dotnet 6 preview with it, and the cli seems to use the latest installed version.

Dotnet format is being added to the cli with dotnet 6 so that seems to be the reason for the change (as per the note here)

[bcallaghan-et]

Thanks for the link to that thread. Having read it, it appears that v5 uses --check while v6 (bundled with the SDK) uses --verify-no-changes.

@AgentEnder The bundled version has several other breaking changes besides the one flag. How do you want to handle the migration from v5 to v6?

[AgentEnder]

Hey @bcallaghan-et, yeah there are a few other breaking changes but I think thats the only one that directly impacts our defaults. For your PR I'd recommend adding some logic that detects if .NET 6 is the installed SDK, and if it is skip the tool install. If it is than also just swap the arg when being passed.

I'll take a closer look at all of the breaking changes in format and see if there is something we can do to help with a more full migration. With .NET 6 being a preview this isn't a huge deal yet, as long as the executors can still run.

Honestly, for now, I could see us detecting the .NET 6 SDK and warning and skipping the actual format, while we get this behavior worked out.