-
Notifications
You must be signed in to change notification settings - Fork 107
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't initialize leaf values when unmarshalling valid shadow paths. (#…
…543) * Don't initialize leaf values when unmarshalling valid shadow paths. Currently when `SetNode` is called on a path, missing elements are initialized as the function traverses through the `GoStruct`. This happens even for paths leading to a leaf as well as shadow paths, causing the default value to always be populated into these elements. This change prevents `SetNode` from initializing a leaf value when traversing a shadow path. * Remove support for arbitrarily-deep shadow paths to reduce complexity * Add tests for checking that shadow paths cannot be non-leaves
- Loading branch information
Showing
2 changed files
with
284 additions
and
361 deletions.
There are no files selected for viewing
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
Oops, something went wrong.