exception occurred about jtoml HOT 4 CLOSED

Fixed in #7, please use version 2.0.0 deployed to Maven.

from jtoml.

Hi eiryu,
The implementation isn't up to date with TOML v0.3.0, which allows additional time formats.
For now you can either use the ISO 8601 full zulu form "1979-05-27T07:32:00Z" (i.e. without offset).
I will try to get the implementation up to date with the most recent - v0.4.0, possibly this week but I can't promise anything.

Cheers,
Asaf

from jtoml.

Hi @eiryu, to catch up with the changes between TOML v0.1.0 to v0.4.0 I will rewrite the parsing of TOML. While at it I will also make a few breaking changes:

• Naming of classes (namely KeyGroup => TomlTable)
• Behaviors on KeyGroup (now TomlTable):
  • toMap - will now behave like localsAsMap, and 'localsAsMap' will be removed.
  • getX - Going doing multiple levels is no longer done with one concatenated string, but each an argument alone. e.g. toml.getBoolean("foo.bar.z") => toml.getBoolean("foo","bar","z") - This is more similar to how you'd use a JSON and is mostly to support non-bare-key names that can now contain "." within them.
  • getAsEnum will also move the enum class parameter to the first position. e.g. getAsEnum("foo.stringKey", TestEnum.class) => getAsEnum(TestEnum.class, "foo","stringKey")
  • getLocalX - all removed.
  • getKeyGroup => getTomlTable

You can look at the work here, it already works vs the v0.1.0 unit tests, but I need to create unit tests for v0.4.0 and make the code work with them.

from jtoml.

@asafh Thanks!!!!

from jtoml.