Skip to content

Missing proper syntax error handling #4

@gubenkoved

Description

@gubenkoved

I came across this project while doing my research on the topic.

I've noticed that even obviously invalid ini files will be silently parsed with incorrect meaning. Wondering if this is by design.

Please find examples below.

# unclosed quoted literal
foo = "bar

# unclosed section
[core
spam = eggs

Parsed into the following data with errors (are they?) silently skipped.

{
  "foo": "\"bar",
  "[core": true,
  "spam": "eggs"
}

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