You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Some diagnostics generated by the LSP when parsing manifest files are not useful to the user.
For example, specifying a dependency like this:
Will produce an error like this:
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
The text was updated successfully, but these errors were encountered: