chore: add schema for typst.toml

[sjfhsjfh]

Maybe create a schema also here?

[laurmaedje]

There are a few more fields. You can find the list here: https://github.com/typst/packages/blob/main/bundler/src/model.rs

The required fields vary between Typst Universe and the local compiler, not sure how to handle that.

Is the filename package.schema.json standard? Do you have some link where I can read up on how things work with these schemas?

[sjfhsjfh]

The required fields vary between Typst Universe and the local compiler, not sure how to handle that.

My purpose for adding this is simple: I can use completion and check in VSCode using Even Better TOML, which searches schema from schemastore. Also there's GitHub Action Support, so I think it depens on what requirements you want users to submit packages that meet I guess, and providing the schema file respectively for Universe and local compiler

Is the filename package.schema.json standard?

To be honest, I'm not quite familiar with this, usually a name like schema.json or version.schema.json is used, and the name is not quite important since schemastore allows self-hosted schema, see here

Do you have some link where I can read up on how things work with these schemas?

• JSON schema tutorial
• schemastore contribution guide
• TOML extension support for json schema

[elegaanz]

From what I understand, it would be better to contribute this file to the schemastore repository directly, so that VSCode
extensions (and maybe other tools) pick it up automatically, without needing to point it to the self-hosted file.

I think the schema should follow what universe does, not what the local compiler does, if we consider that this schema is useful to get editor completions and diagnostics: I think that most of the time when you edit a typst.toml it will be submitted to Universe at some point. Maybe another schema file with only compiler-required fields marked as such could still exist alongside the main one, to make it possible to run lighter checks by giving an explicit schema path (I believe this is something you can do with most tools that work with JSON schemas).

If you open a PR on the schemastore repository, you can ping me in the discussion over there, I will happily give it a look.