Fix For OAPH nullable values not set null after initial value#69
Merged
ChrisPulman merged 1 commit intomainfrom Sep 30, 2024
Merged
Fix For OAPH nullable values not set null after initial value#69ChrisPulman merged 1 commit intomainfrom
ChrisPulman merged 1 commit intomainfrom
Conversation
ChrisPulman
changed the title
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
What kind of change does this PR introduce?
Fix
Closes #63
What is the current behavior?
OAPH values using nullable types and a default value will revert to the default value if the Observable results in a null value
What is the new behavior?
Fix For OAPH null values when set null after initial value now allows null values to be propagated upon a null value being set from the connected Observable.
What might this PR break?
Where previously the default value would have been return now the correct value will be returned.
Please check if the PR fulfills these requirements
Other information: