Shall we support to cal dotnet-format global tool in some way?

[liny01-nbsa]

I want to use this with my legacy .Net Framework project. But I'm running into issue setting this action up.

As mentioned in this documentation:

I have tried to fork and make a change to the way linter is called, however, I run into issue:

But when I run the command directly it does work:

I love the part your lint-action is able to capture the results and present it in a nice format. I would like to use this action directly.

Can dotnet-format call be supported directly?

[ocean90]

@ahanoff or @AndrewBabbitt97 can you help here?

[andrewbabbittdev]

Getting .NET Framework support in upstream is likely what should actually be done if possible, I'd probably start with a issue on the dotnet-format repo.

As for potential of adding support for the global tool, would probably be best to have it just be an additional option on the existing linter if possible so were not just copying code (DRY). Opinions @ocean90 ?

[ocean90]

Is it only the command that needs to be changed or also any parameters? The action already has [linter]_command_prefix so we could think about adding a [linter]_command input which lets your override the default command, in this case dotnet format with dotnet-format.

[andrewbabbittdev]

I would lean towards adding a [linter]_command input. The available parameters are different between cli versions, however not in a breaking manner in relation to this action.

[liny01-nbsa]

Shall we create an issue for tracking?

[andrewbabbittdev]

I'll probably go try and get some of this work started this weekend.

On another note I discovered documentation linting errors do not show up at all with lint-action but do when running dotnet format over the past week, so I want to go implement a test case for this as well and figure out why lint-action isn't picking them up.