Skip to content

Valid TOML now rejected as redefining a table #54

@vlas-voloshin

Description

@vlas-voloshin

After updating to v.0.3.0, the following TOML is now rejected by the decoder:

[one.two]
hello = "world"

[one.two.three]
foo = "bar"

with an error:

  • Value |4, 15| Using dotted keys to add to [one.two] after explicitly defining it above is not allowed"

I see references to invalid combinations of implicitly/explicitly defined tables in TOML spec v.1.0.0, and compliance tests (1, 2) around that structure, however I don't see anything in the spec that restricts extending a table like the example above shows. In fact, toml++ v.3.4.0, via TOMLKit, indeed accepts this structure.

As such, this seems like a regression to me, introduced in #53. Am I missing something? Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions