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.

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

[bug] mixed notation of objects with { } and . lead to null #28

Open
andreaTP opened this issue Nov 28, 2017 · 3 comments
Open

[bug] mixed notation of objects with { } and . lead to null #28

andreaTP opened this issue Nov 28, 2017 · 3 comments

Comments

@andreaTP
Copy link
Member

minimal repro:

  @Test
  def parseNestedObjectsWithMixedNotations() = {
    val config = ConfigFactory.parseString("a { b.c { d = 1 } }")

    assert { config != null }

    assertEquals(config.getConfig("a.b.c").getInt("d"), 1)
  }

this will fail throwing a NPE

@andreaTP
Copy link
Member Author

@mliarakos
Copy link
Contributor

Bump on this issue. I encountered it adapting configs for lagom.js. I removed the mix notation as a work-around.

@andreaTP
Copy link
Member Author

Completely forgot to take a closer look at this, thanks for the heads up @mliarakos !

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