feat: add sub-path support to mutator and retriever #12
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
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.
Add support for sub-paths (e.g. 'file.metaData.path'). Should not conflict with indexed paths e.g. 'person.addresses.0' or 'person.addresses.private'. The former has a numerical index and is thereby ignored, the latter is not as straightforward. When retrieving data we check if the index ('path') exists on the property ('metaData'). Indexed properties should always be non-associative array and thus there is no match. When setting data we can check the value. If the value is an associative array we must assume it's an indexed path and process it as such. Hence it is not possible to use an associative array as a value for a sub-path (but I don't think that's a common use case).
Fixes #2