Skip to content

Wrong result for this hocon #92

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.

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

Closed
iron9light opened this issue May 30, 2019 · 1 comment
Closed

Wrong result for this hocon #92

iron9light opened this issue May 30, 2019 · 1 comment

Comments

@iron9light
Copy link
Contributor

Input:

x={ q : 10 }
y=5

a=1
a.q.r.s=${b}
a=${y}
a=${x}
a={ c : 3 }

b=${x}
b=${y}

// nesting ConfigDelayed inside another one
c=${x}
c={ d : 600, e : ${a}, f : ${b} }

The parsed value should be something like:

{
    "a" : {
        "c" : 3,
        "q" : 10
    },
    "b" : 5,
    "c" : {
        "d" : 600,
        "e" : {
            "c" : 3,
            "q" : 10
        },
        "f" : 5,
        "q" : 10
    },
    "x" : {
        "q" : 10
    },
    "y" : 5
}

But the c.e.q does not existed in parsed result.

@Arkatufus
Copy link
Contributor

Working on a fix, thank you for reporting.

Arkatufus added a commit to Arkatufus/HOCON that referenced this issue Jun 4, 2019
…ects may not return the proper object value in certain circumstances.
Aaronontheweb pushed a commit that referenced this issue Jun 6, 2019
…the proper object value in certain circumstances. (#93)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants