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
Hey there. Thanks for adding XamlStyler.Console to NuGet, I've integrated it with my project and now my XAML files are formatted on every build. I'm no longer bound to Visual Studio and can now use Rider, yay. Good job!
Anyway, it would be really nice if the console tool would also accept individual formatting settings as command line options. Currently it accepts a path to a configuration file (or infers it automatically) but it's not super convenient if you just want to set 1 option.
I like how Prettier did it, they have default settings, configuration file and command line arguments, and the priority goes like this (first to last):
Command line arguments -> Config file -> Default settings.
That means both config file and command line arguments can coexist and there's no need for some extra validation.
If this issue is approved and there's no one willing to take it, I can probably make a PR to implement this.
The text was updated successfully, but these errors were encountered:
Great idea! What are your thoughts on support for AttributeOrderingRuleGroups as a command line argument? IMO, it is relatively complex compared to all other options, and I am not sure if there is as clear of a benefit with this one as with all the other settings.
Hey there. Thanks for adding XamlStyler.Console to NuGet, I've integrated it with my project and now my XAML files are formatted on every build. I'm no longer bound to Visual Studio and can now use Rider, yay. Good job!
Anyway, it would be really nice if the console tool would also accept individual formatting settings as command line options. Currently it accepts a path to a configuration file (or infers it automatically) but it's not super convenient if you just want to set 1 option.
I like how Prettier did it, they have default settings, configuration file and command line arguments, and the priority goes like this (first to last):
Command line arguments -> Config file -> Default settings.
That means both config file and command line arguments can coexist and there's no need for some extra validation.
If this issue is approved and there's no one willing to take it, I can probably make a PR to implement this.
The text was updated successfully, but these errors were encountered: