Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ensure dont lose sibling keys when ask for top level object and child… #473

Merged
merged 2 commits into from
May 15, 2020
Merged

Ensure dont lose sibling keys when ask for top level object and child… #473

merged 2 commits into from
May 15, 2020

Conversation

snewcomer
Copy link
Collaborator

@snewcomer snewcomer commented May 14, 2020 •
edited
Loading

@snewcomer snewcomer added the bug label May 14, 2020
@snewcomer snewcomer self-assigned this May 14, 2020
@snewcomer snewcomer merged commit 031a63a into master May 15, 2020
@snewcomer snewcomer deleted the sn/sibling-keys-loss branch May 15, 2020 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@snewcomer snewcomer

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Setting value deeper than depth 1 removes siblings
1 participant
@snewcomer