chore(deps): update dependency csharpier to v1 #12
No reviewers
Zenith/Developers
Labels
No labels
Area/Backend
Area/Frontend
Area/Integration
Area/Models
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Renovate
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Zenith/ZenithInfo-Legacy!12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/csharpier-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.30.6->1.1.2Release Notes
belav/csharpier (csharpier)
v1.1.2Compare Source
What's Changed
Inconsistencies with null-coalescing wrapping on method chains #1573
On longer method chains, depending on the exact chain a null coalescing expression wouldn't always be preceded by a new line.
Full Changelog: https://github.com/belav/csharpier/compare/1.1.1...1.1.2
v1.1.1Compare Source
What's Changed
Unhandled exception: System.ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex') #1673
CSharpier was throwing an exception when formating a directory contained a file without an extension.
Full Changelog: https://github.com/belav/csharpier/compare/1.1.1...1.1.1
v1.1.0Compare Source
What's Changed
.gitignore from parent folders impacts formatting of children #1627
CSharpier will no longer consider
.gitignorefiles located above the root of the current git repository.Changes to stdin formatting #288 #1657
There is a new option
--stdin-filepaththat is used to specify the filepath CSharpier should use for resolving options and ignore files.When no path is specified via
stdin-path<in which case it is assumed to be xml.Support for C# 14 and .NET 10 #1654 #1646
Changes were required to support the following
Support --ignore-path CLI option #1585
It is now possible to specify the path to an ignore file
Format xaml and slnx by default #1628 #1604
CSharpier now formats
xamlandslnxby default without the need for configuration changes.XML formatting is not taking into account EOL configuration on multiline comments #1660
When formatting the following XML, CSharpier would always use the system system default for ending lines within the comment instead of the respecting the configured EOL setting.
Error when no read access to intermediate containing folder #1656
In the case that CSharpier had access to a sub directory but not the parent of that sub directory, it was failing with an exception. That has been resolved.
Misleading message after "csharpier check" #1645
Previously the
formatandcheckcommands both used the same output message. Thecheckcommand now correctly reports that it checked files and did not format them.v1.0.3Compare Source
dotnet csharpier check .
Formatted 13226 files in 21986ms.
v1.0.2Compare Source
What's Changed
Performance issues when supporting .gitignore. #1588
CSharpier was using a naive algorithm for parsing and evaluating gitignore rules that caused significant perfomance issues. @kevinboss reworked the implementation to drastically increate performance.
Exclude
bin/andobj/directory content from xml formatting #1600CSharpier now excludes all files in
bin/andobj/by default.Error on syntactically valid conditional with
is#1612The following c# is valid and compiles with
9.0.300+. CSharpier was updated to properly parse it.Xml formatting with comments in text element inserts extra new lines #1607
CSharpier has some issues with formatting text that contained xml comments. That has been improved.
Input & expected output
1.0.1
Inconsistent formatting of single-line lambda expressions #1594
CSharpier
1.0.0introduced a regression that caused the following formatting. This is now working as expected.Full Changelog: https://github.com/belav/csharpier/compare/1.0.1...1.0.2
v1.0.1Compare Source
What's Changed
CSharpier's support for .gitignore is causing performance issues #1584
The support for
.gitignorehas some major performance problems when there are a large number of.gitignorefiles and/or ignore rules. The feature has been disabled for now until it can be fixed.CSharpier.MsBuild issues #1586
CSharpier.MsBuild was not properly logging errors when performing a formatting check. This would result in the build passing when files were not formatted.
Setting
CSharpier_LogLevelwas passing an invalid parameter of--loglevelto CSharpier, resulting in a build failureFull Changelog: https://github.com/belav/csharpier/compare/1.0.0...1.0.1
v1.0.0Compare Source
Major Changes
Support for formatting XML #819
CSharpier now formats xml files by default. It will try to format ".csproj", ".props", ".targets", ".xml", ".config" as if they were xml.
If a file is not valid xml it will be treated as a warning.
The default indent size is
2instead of4Performance Improvements
@TimothyMakkison put a lot of effort into improving the performance of CSharpier. These benchmark numbers show drastic improvement for both speed and memory usage.
Baseline
After Improvements
Breaking Changes
ConfigurationFile - rename TabWidth to IndentSize #1377
In order to get consistency between an
.editorconfigand.csharpierconfigthe optionTabWidthhas been renamed toIndentSize. This is also a more accurate name considering by default indentation is done with spaces and not tabs.Rework the CLI to use commands and arguments. #1321
The CLI has been reworked to use commands. This helps make it clear which arguments apply to which commands. The two common commands are below, see https://csharpier.com/docs/CLI for more details.
Changing the tool command to csharpier. Changing the assembly/exe to CSharpier #1418
Prior to
1.0.0the tool command wasdotnet-csharpierand assembly/exe were nameddotnet_csharpier.The tool command name was changed to just
csharpierdotnet csharpier --versioncsharpier --versionThe assembly/exe names have changed to just
CSharpierSupport for ignoring files via a .gitignore #631
CSharpier now works as follows when determining if a file should be ignored.
What's Changed
Add logging format argument and support for msbuild logs #1517
CSharpier now supports a
--log-formatargument. By default it will log with a console format.With
--log-format MsBuildCSharpier will produce logs in a format that allow jumping to files in the VisualStudio error list.Thanks go to @moormaster for the contribution
Allow passing an
.editorconfigfile path into--config-path#1456CSharpier now supports passing a path to an
.editorconfigfile when using the--config-pathargument.Always ignore any files in .git folder #1438
CSharpier will now ignore any files that are in a
.gitfolder. Previously if the.gitfolder happened to contain an invalid c# file CSharpier would attempt to format it and report an error.Avoid excessive file system watches for --server #1465
When CSharpier server was started, it would create file watches for all of the files within the directory the tool existed in. This can lead to some systems running out of the ability to monitor more files.
CSharpier server now uses a temporary empty content root to avoid creating all file watches.
Thanks go to @chklauser for the contribution
Smarter EditorConfig parsing #1228
Previously CSharpier was eagerly loading all
.editorconfigfiles within a directory that it was asked to format. It now lazy loads them in a way that is performant and avoids loading and parsing editorconfigs that aren't needed.Extra blank line before local scope block in global statement #1566
Inconsistent indentation for parenthesis expression #1562
A statement being surrounded by parentheses affected the indentation in an inconsistent way.
Attribute on property accessor causes unnecessary newlines in formatting #1558
The logic around when to break properties with attributes has been adjusted. See the example for more details
Fluent multiline with comment re-formats incorrectly. #1556
When a single method in a fluent chain was commented out, csharpier would try to collapse the chain to a single line.
Comments on an invocation chain that began with a generic where breaking when they should not #1555
In some cases CSharpier was breaking an invocation chain when it should not.
Comment in line before attribute causes unexpected line break after attribute #1553
CSharpier was breaking and indenting a parameter when it had a comment
Huge oneliner with switch expression followed my method invocations #1546
CSharpier was keeping a method chain on a single line if it was invoked on a switch expression within parentheses.
Inconsistent Formatting of Single Parameter Lambda Expressions #1522
CSharpier was not formatting all lambda expressions consistently when they were the single argument to a method call.
Empty lines after XmlComments should be removed #1521
When a member has documentation comments, any empty lines after those comments and before the member are now removed.
CSharpier always includes indentation whitespace on non-content lines #1455
CSharpier was indenting the final non-content line within a raw string. It now leaves them dedented to keep it consistent with other non-content lines.
Full Changelog: https://github.com/belav/csharpier/compare/0.30.6...1.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
eb09bde20dto2344669e33b5acfd0b13to8c026b6b1a8c026b6b1ato74fff3f1e874fff3f1e8toaef492443caef492443cto4378d5e1254378d5e125toa71b67a288a71b67a288toec2c35b104ec2c35b104toa75c24a7efa75c24a7eftoce0f3a6248View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.