Skip to content

[FEATURE] Improve manifest TOML parsing diagnostics #34

@SpontanCombust

Description

@SpontanCombust

Some diagnostics generated by the LSP when parsing manifest files are not useful to the user.
For example, specifying a dependency like this:

content0 = { paths = "../content0" } #mind the typo "paths" instead of "path"

Will produce an error like this:

TOML file parsing error: TOML parse error at line 11, column 8
   |
11 | content0 = { paths = "../content0" }
   |            ^^^^^^^^^^^^^^^^^^^^^^^^^
data did not match any variant of untagged enum DependencyValue

It is safe to say that use would have no idea what to do about this "untagged enum DependencyValue".

The error should rather say something along the lines of

"path" key not found

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or request

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions