Allow disabling of merging restrictions with base in configuration #528
Conversation
This file contains 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
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #528 +/- ##
==========================================
- Coverage 94.17% 94.08% -0.09%
==========================================
Files 21 21
Lines 3159 3164 +5
Branches 495 496 +1
==========================================
+ Hits 2975 2977 +2
- Misses 120 122 +2
- Partials 64 65 +1 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
v2.1.954has been a breaking change due to the merging of restrictions in 4539c1e.As a result, properties with numeric restrictions were previously generated as string and now generated as numeric types (byte/ushort/uint/int/long/etc.). This configuration allows projects to update to the latest version gradually with the ability to opt-out from the new behaviour temporarily.
With the configuration, projects using the package can update to the latest version in 2 parts, one with only changes to comments and attributes, and after that with only changes in the generated property types.