Repro for a bug with null assignment #1706
Merged
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
exyi
force-pushed
the
fix/nullable-command-change
branch
from
e9f5ff6 to
4ec49ac
Compare
exyi
force-pushed
the
fix/nullable-command-change
branch
from
4ec49ac to
7edbc96
Compare
exyi
approved these changes
Oct 7, 2023
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.
I've found a bug, probably in the binding parser -
NullableProperty = nulldoesn't work as expected - instead of assigningnullto the property, it assigns the default value for its unwrapped type.Repro sample is here:
/FeatureSamples/ViewModelDeserialization/PropertyNullAssignment