[YAML] Path resolution failing if a key is numeric

[dkambersky]

I apologise if this is intended and documented somewhere, I couldn't find it mentioned anywhere.
Consider this yaml config file:

tree:
  1:
    myVal: true

This will fail to resolve properly (i.e. config.at("tree.1.myVal").toValue<Boolean>())).
However, if that 1 is renamed to a1, everything works properly.

[uchuhimo]

@dkambersky Thank you for your report! I have fixed it in a new release v0.22.0. Please have a try.

[dkambersky]

Thanks for the quick response. It seems like it fails for values over an int's max value - e.g. 484444731619803154. The exact error thrown is

com.uchuhimo.konf.PathConflictException: "tree.484444731619803154.key" conflicts with existed paths in the tree node.

[uchuhimo]

@dkambersky Yes, it only support int now. You can use "484444731619803154" instead of 484444731619803154 to work around it, E.g.,

tree:
  "484444731619803154":
    myVal: true

Is it necessary to support such a large number in your use case? If not, I will delay long / BigInteger support to the next release with other features/bugfixes.

[dkambersky]

It is really important to me - some of the keys I use are related to Discord IDs of various elements (ie guilds, users) , which are Longs. If it would take long to implement I'm not going to keep you from working on the main update though. Thanks!

…

On Mon, 23 Dec 2019, 06:12 uchuhimo, ***@***.***> wrote: Reopened #45 <#45>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#45?email_source=notifications&email_token=AAIAJ2XTMCHQEWA723KQSVTQ2BCDPA5CNFSM4J6JA6ZKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVUKJUEQ#event-2903808530>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIAJ2WD5O53SVIZ6WX5AVLQ2BCDPANCNFSM4J6JA6ZA> .

[uchuhimo]

@dkambersky I release a new version v0.22.1 that fixes the problem. Please have a try.

[dkambersky]

Same error unfortunately :( But I'll just use the string workaround for now, thanks again for being this fast to respond!

[uchuhimo]

@dkambersky I have added your example code as tests and all the tests are passed (see https://github.com/uchuhimo/konf/blob/master/konf-yaml/src/test/kotlin/com/uchuhimo/konf/source/yaml/YamlSourceLoadSpec.kt#L44-L73). Thus I believe the error has been gone. Would you like to provide your code that still has the same error?

[dkambersky]

I'm sorry, that was my own oversight. It's working fine now. Thanks for the fix!