Repository navigation
Set() with key pointing to nonexistent map path - #66
Merged
Merged
Conversation
âĶ, the path will be created.
hanzei
self-requested a review
April 13, 2018 13:45
Collaborator
|
@earncef That you for your contributions. I`m currently on vacation and will into them next week. |
Collaborator
Author
|
No worries. Take all the time you need. |
hanzei
changed the title
This file contains hidden or 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.
When calling Set() on a nonexistent map path, the path can be created quite easily in case of MSIs.
I have not written an implementation for arrays, as that might be problematic in case of keys like obj.Set("a.b[10000].c", ...)