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

tryResolve can leave an object node in a bad state #668

Merged
merged 2 commits into from
Mar 7, 2018
Merged

tryResolve can leave an object node in a bad state #668

merged 2 commits into from
Mar 7, 2018

Commits on Feb 19, 2018

  1. tryResolve can leave an object node in a bad state 

    if you `tryResolve(node, '/path_that_doesnt_exist')`, _autoUnbox is left === false
Doesn't make sense to have any simple `get` operations breaking the tree.
    @dnakov
    dnakov authored Feb 19, 2018
    Configuration menu
    Copy the full SHA
    26f772a View commit details
    Browse the repository at this point in the history

  2. fix bad return statement

    @dnakov
    dnakov authored Feb 19, 2018
    Configuration menu
    Copy the full SHA
    2bb05e6 View commit details
    Browse the repository at this point in the history