-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected error in app.toml
#457
Comments
I have the same problem with file conf.toml. Whole is red and full of |
I think the fact that the plugin is magic is more often useful than not. I expect most people to use TOML files to configure well-known tools with a schema defined, rather than custom TOML files with conflicting naming with well-known files. However, it should be easy to disable schema on a per-file basis, but it doesn't seem to be the case. It's possible to set I think it would also be nice to have the |
Yes, it is right. But I am not sure it is well-known... So what is the |
Get it. But I still do not think it's well-known. |
Yes, I agree not all schemas in the catalog have the same weight and being able to easily disable or overwrite a schema is an important feature, as mentioned in #457 (comment) already. However, this will need a PR. I've already added the |
same problem with I want the schema to stay enabled for |
When I opened
app.toml
, Even Better TOML told me that thatAdditional properties are not allowed ('pid' were unexpected)
. But if I changed its name, it didn't show any error message anymore. I guess there must be some schema on the especial file namedapp.toml
but I guess it is not expected for everyone.The text was updated successfully, but these errors were encountered: