Bump csharpier from 1.2.6 to 1.3.0#157
Conversation
--- updated-dependencies: - dependency-name: csharpier dependency-version: 1.3.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Coverage variation | ✅ +0.00% coverage variation (-1.00%) |
| Diff coverage | ✅ ∅ diff coverage |
Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (60b2fd6) Report Missing Report Missing Report Missing Head commit (5e3d394) 1 (+0) 1 (+0) 100.00% (+0.00%) Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>
Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#157) 0 0 ∅ (not applicable) Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
1 Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
guibranco
left a comment
There was a problem hiding this comment.
Automatically approved by gstraccini[bot]
|
|
✅ Build pagarme-sdk-dotnet 1.0.625 completed (commit cf895c1dfc by @dependabot[bot]) |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #157 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 1 1
=========================================
Hits 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|



Updated csharpier from 1.2.6 to 1.3.0.
Release notes
Sourced from csharpier's releases.
1.3.0
1.3.0
Breaking Changes
Change xml formatting to return error when it runs into syntax error so it is consistent with c# #1854
Previously CSharpier treated an invalid xml file as a warning instead of an error. This was inconsistent with how it treated c# files.
Invalid c# or xml files are not treated as errors.
The
--compilation-errors-as-warningsargument has been renamed to--syntax-errors-as-warningsand can be used to return warnings instead of errors when encountering invalid files.What's Changed
Feature: Configurable whitespace handling for xml #1790
CSharpier now supports two types of xml whitespace formatting strict or ignore.
By default all xml except
xamloraxamlis treated as strict whitespace. See detailsFeature: Move closing bracket for xml elements to the same line. #1598
With strict xml whitespace handling, csharpier now keeps the closing bracket for an element on the same line instead of breaking it to a new line.
Feature: Support for csharpier-ignore with XML formatter #1788
CSharpier now supports
csharpier-ignorein xml files. See detailsFeature: Add MSBuild transitive and multi-target support #1833
CSharpier.MSBuild can now work as a transitive dependency.
Feature: allow checking formatting with cache #1830
The
csharpier checkcommand now supports a--use-cacheoption.Feature: remove dependency on Microsoft.AspNetCore.App #1508
Previously CSharpier required that Microsoft.AspNetCore.App be installed. CSharpier has been modified to use an HttpListener when it is run using
serverto remove the need for this dependency.Fix: csharpier-ignore comment removes linespaces before block #1867
CSharpier was removing blank lines before csharpier-ignore comments in some cases