element types tryparse nullability #2752
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
…nullability # Conflicts: # src/Hl7.Fhir.Base/ElementModel/Types/Boolean.cs # src/Hl7.Fhir.Base/ElementModel/Types/Quantity.cs
Kasdejong
changed the title
ewoutkramer
requested changes
Apr 4, 2024
ewoutkramer
approved these changes
Apr 9, 2024
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.
Description
Made all out variables of ElementModel/Types classes' TryParse methods nullable. Added annotations indicating they are not null when the method returns true.
Related issues
Closes #2749
Testing
Added unit tests to check if an invalid string indeed leads to a null value in the out variable