-
-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for support of custom file extensions to scan/fix #1220
Milestone
Comments
I have a PR with partly implemented csproj formatting and had the same idea because it made sense to allow someone to use that formatter for xml, props, etc. I'll work on getting the ability to specify formatters for other extensions it into the next release. One possibility
Or maybe support it with
I should also take a look at how prettier does this. |
belav
added a commit
that referenced
this issue
May 3, 2024
…her file extensions to be formatted. closes #1220
belav
added a commit
that referenced
this issue
May 12, 2024
…her file extensions to be formatted. closes #1220
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Request
As it currently stands, it is not possible to scan C# files that have custom extensions (for build/deployment processes etc.)
The only work around for this, is to have a special script/process: that changes the extension, runs CSharpier, then puts the extension back.
Concept
Add a config section to the '.csharpierrc.*' that allows the user to pick the file extensions to target ie.
The text was updated successfully, but these errors were encountered: