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
It would be great if we are able to check, if XamlStyler was applied to the xaml files. I would like to add a stage to my CI build which breaks, if anyone forgot to apply the style rules.
Is there anything like that? Otherwise, I’ll have a look at it.
The text was updated successfully, but these errors were encountered:
Have you explored some of the script integration options? A team that I worked on utilized a Git Hook to enforce format on commit. It could easily be adapted to run as a build task in a CI build.
Yes, I have seen the script integration options and I'm already using them with Cake. However, I don't want to use Git hooks. I'm not sure if VSTS support those kind of server side Git hooks and I don't want to rely on client side hooks.
I would like to make sure that the code is formatted correct before it gets merged into the main branch without any bypass (I know these feature from other projects like diffplug/spotless). A simple check option for XamlStyler.Console would be enough. For example, we can easily compare originalContent with formattedOutput and break the build or use a specific exit code.
This seems like a reasonable feature request for the console app.
For example, we can easily compare originalContent with formattedOutput and break the build or use a specific exit code.
Edit: Updating title to reflect specific feature request.
grochocki
changed the title
Check if style changes are necessary
Add option to XamlStyler.Console to perform a formatting check without changing output
Feb 9, 2019
It would be great if we are able to check, if XamlStyler was applied to the
xaml
files. I would like to add a stage to my CI build which breaks, if anyone forgot to apply the style rules.Is there anything like that? Otherwise, I’ll have a look at it.
The text was updated successfully, but these errors were encountered: