fix: keep nil values during (de)serialization #14127
Merged
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
Sets
IsNullable = true
to inXmlElement
attribute for reference properties if they are defined as nillable in xsd.Known limitations
Since we're using c# model, when desiralizing XML and serializing it back back, we can't always reproduce the same same XML.
Example
According to xsd schema:
following XML is valid since minOccurs is set to "0":
But when deserializing and serializing it back we'll produce following XML:
Since the node type is string, functionally XMLs will be equivalent.
Related Issue(s)
Altinn/app-lib-dotnet#911
Verification
Documentation