Update pattern to match current dotnet format output
#491
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update to use node20 instead of node16
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change brings the problem matcher in sync with current output format of
dotnet format, and as it happens alsodotnet buildas they share a format now. So it'll catch both linting errors as well as build warnings.Besides that it adds a missing copy to the publish stage to make sure the json file makes its way to the
distfolder. I've also updated this to target Node 16 instead of 12. The readme is also updated with up-to-date guidance.This shows examples of the updated regex working on both formatting output as well as build warnings: https://regex101.com/r/OYkSSv/1