SCJ-000: Bump csharpier from 0.27.3 to 0.30.6 #287
+2
−2
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.
Updated csharpier from 0.27.3 to 0.30.6.
Release notes
Sourced from csharpier's releases.
0.30.6
What's Changed
Trailing comma is placed on new line if last enum value is followed by a comment #1429
Full Changelog: belav/csharpier@0.30.5...0.30.6
0.30.5
What's Changed
Extra blank line added to file each time csharpier runs on this file #1426
When a file ended in a comment and that comment had multiple blank lines before it, a new blank line was being added each time it was formatted.
// input
CSharpier keeps adding a newline every time a file is formatted #1408
In some cases if a file ended with a comment, CSharpier would add a new extra blank line above the comment each time it formatted the file
Full Changelog: belav/csharpier@0.30.3...0.30.4
0.30.3
What's Changed
CSharpier.MsBuild doesn't fail the github action anymore #1357
The changes for 1311 caused CSharpier.MsBuild to not report unformatted files as errors on linux.
Thanks go to @PetSerAl for the fix
0.30.2
What's Changed
CSharpier.MsBuild now uses DOTNET_HOST_PATH instead of just dotnet #1387
Use current dotnet binary from DOTNET_HOST_PATH instead of just dotnet.
https://github.com/dotnet/roslyn/blob/324fd25331c969cd742ba68eee09ffd4b6fd29e3/src/Compilers/Shared/RuntimeHostInfo.cs#L61-L64
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-environment-variables#dotnet_host_path
Collection expression inside a dictionary adds unexpected new line #1390
Failed syntax tree validation reported when trailing comma added before a trailing comment #1388
With the following code, CSharpier will add a trailing comma before the trailing comment.
CSharpier's syntax tree validation was incorrectly reporting this as a failure.
Adds additional space before each member access in verbatim interpolated multiline string #1358
When an interpolated verbatim string contained line breaks, the code within the interpolations would contain extra spaces.
csharpier-ignore-startnow supported in object initializers #1342Fixed extra new line between cast and collection expression. #1334
Process cannot access the file "....net8.0\any\server.log" while running multiple extensions. #1324
CSharpier Server now uses a log file name based on the port that it is starting on to avoid concurrency issues trying to access the same log file
Full Changelog: belav/csharpier@0.29.0...0.29.1
0.29.0
Breaking Changes
The formatting command will now exit with an error code of 1 if one of the target files cannot be compiled #1131
Prior to 0.29.0 if csharpier encountered a file that could not be compiled it would treat it as a warning and exit with a code of 0.
As of 0.29.0 a file that cannot be compiled is now treated as an error and csharpier will exit with code 1
What's Changed
Enforce trailing commas in object and collection initializer #668
CSharpier will now add trailing commas automatically where appropriate. It will collapse to a single line and remove the trailing comma in cases where everything fits on one line.
Many thanks go to @dawust for the contribution.
Support for formatting custom file extensions #1220
Prior to 0.29.0 csharpier would only format files with an extension of .cs or .csx. It is now possible to configure csharpier to format other files extensions, and to specify configuration options per file extension.
See https://csharpier.com/docs/Configuration#configuration-overrides for more details.
Invalid blank line being added with lambda returning collection expression #1306
... (truncated)
0.28.2
What's Changed
Pipe to
dotnet csharpierfails when subdirectory is inaccessible #1240When running the following CSharpier would look for config files in subdirectories of the
pwd. This could lead to exceptions if some of those directories were inaccessible.Thanks go to @jamesfoster for reporting the issue.
Full Changelog: belav/csharpier@0.28.1...0.28.2
0.28.1
What's Changed
Third party .editorconfig leading to: Error Failure parsing editorconfig files #1227
When CSharpier encountered an invalid
.editorconfigfile, it would throw an exception and not format files. These files could appear in 3rd party code (for example within node_modules). CSharpier now ignores invalid lines in.editorconfigsThanks go to @K0Te for reporting the issue
Full Changelog: belav/csharpier@0.28.0...0.28.1
0.28.0
What's Changed
Fix dedented method call if there is a long chain #1154
In some cases of method chains, the first invocation would end up dedented.
Extra newline in switch case statement with curly braces [#1192](belav/csharpier#1192
If a case statement started with a block it would get an extra new line