dotnet-format: accept a list of files to format (instead of a full workspace) about format HOT 9 CLOSED

@BhaaLseN you did the right thing. I just put this repo together recently

from format.

This is available on myget version 3.0.4-prerelease.19171.3 and later

dotnet tool install -g dotnet-format --version 3.0.4-prerelease.19171.3 --add-source https://dotnet.myget.org/F/format/api/v3/index.json

from format.

@JoeRobich or @jinujoseph can you move this to https://github.com/dotnet/format?

from format.

Oh, nice, didn't know there was a repository dedicated to dotnet format; created the issue on roslyn since it had other related issues.
Thanks for moving it 👍

from format.

@jmarolf @JoeRobich I was thinking of looking into this, as it's something I could use too. Is the way it's written in the above intended use case the way to move forward? Is a --files option necessary or would providing paths as arguments to the command be enough?

from format.

Personally, my gut tells me dotnet format Program.cs should just format Program.cs without requiring a parameter. dotnet format Sample.csproj doesn't work and requires the use of -w/--workspace, so the parameter-less invocation seems free for grabs (unless this is a limitation of invoking commands using dotnet).
I'm fine with either though; but I'm not sure if passing filenames as command line will ever run into issues on any of the supported OS (due to length restrictions or whatever).

from format.

@BhaaLseN When thinking long-term, I agree with you. Currently we get some benefits from using the MSBuildWorkspace to enumerate projects and documents as well as saving changes, which requires a project or solution file.

@challen0 I think the easiest path to get this in would be to:

• Require that a workspace (a single project or solution file) be discoverable in the current directory or specified with the -w flag (as currently is the case)
• Add a --files flag that accepts a comma separated list of file paths
• Globs are not currently supported
• When processing documents in a project, if --files were specified, check that the document path ends with one of the file paths before formatting.

from format.

Pass that file list as command line parameters into dotnet format (or try to pipe them into stdin)

In order to format list of files that I have just committed, I am using the following command before pushing my changes upstream:

dotnet-format --files $(git show --name-only --pretty="" | tr '\n' ',')

(followed by git add . && git commit --amend)

It would be great if we can pipe the files one by one:

git show --name-only --pretty="" | dotnet-format --files

or simply

git show --name-only --pretty="" | dotnet-format

and/or even: git show --name-only --pretty="" | dotnet-format - (minus sign in the end implying read-from-stdin)

i.e. without needing to join the list as comma separated and read path from stdin.

from format.

@am11 can you file a new issue for that request? Thanks!

from format.