Entity->hasValue() should not set null value for uninitialized property #514
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.
Entity->hasValue()
should not set value for property which does not have value yet. In most cases it will just set null and gets eventually overriden, but in case of enum wrapper which expects fixed subset of values, null (which is out of that subset) raises an exception when enum is tried to be created.To verify issue, drop the source change in ImmutableDataTrait - included test will fail.