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.
Moving JsonProperty declaration to getters to avoid duplicate fetch in serialization/deserialization scenarios
PR Details
Description
This PR moves the "@JsonProperty" declaration in the NodeSetXY and Nodes classes to their respective getters rather than the private property declaration. For some reason, having those on the private property exposed that private property when serializing/deserializing and as a result both the private property and the public getter method were called - causing paths to come out as duplicated.
Related Issue
Motivation and Context
Solves problem described in description
How Has This Been Tested?
Tested locally, and in WYDOT test environment
Types of changes
Checklist:
ODE Contributing Guide