fix: Nullable<T>.Value is no longer treated as a member
#575
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 Report
@@ Coverage Diff @@
## main #575 +/- ##
==========================================
- Coverage 91.09% 91.08% -0.01%
==========================================
Files 167 167
Lines 5669 5656 -13
Branches 716 716
==========================================
- Hits 5164 5152 -12
+ Misses 352 351 -1
Partials 153 153
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
latonz
requested changes
Jul 18, 2023
test/Riok.Mapperly.Tests/Mapping/ObjectPropertyFlatteningTest.cs
Outdated
Show resolved
Hide resolved
TimothyMakkison
force-pushed
the
null_value_571
branch
from
8f39cb3
to
fd13d12
Compare
latonz
approved these changes
Jul 18, 2023
|
🎉 This PR is included in version 2.9.0-next.4 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 3.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Nullable<T>.Valueis no longer treated as a memberDescription
Added check to
SymbolAccessorfor nullable value types. This wayNullable<T>.Valuewill not be treated as a member resulting in invalid auto resolved flatteningsFixes #572 & #571
Checklist