Prevent incorrect merge of nested maps in metadata #936
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.
Goal
Prevents the incorrect merging of nested maps in the
Metadata
class. This manifested as the same key-value pair being added to the incorrect location multiple times.Changeset
The
Metadata
class now only attempts to merge values if they are both metadata maps. AdditionallymergeMaps
now takes the correct first parameter - previously the entire section was passed rather than the existing map value.Testing
MetadataSerializationTest
which was incorrectly asserting the previous behaviour