Skip to content
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

TOML schemas #35

Open
jesseditson opened this issue Sep 17, 2024 · 2 comments
Open

TOML schemas #35

jesseditson opened this issue Sep 17, 2024 · 2 comments

Comments

@jesseditson
Copy link
Owner

When editing an archival site in VSCode or another editor that supports TOML Schemas, it would be nice if you got validation on your objects and the archival types.

The archival repo would publish schemas for:

  • manifest.toml
  • objects.toml

Then, during build/rebuild, archival should emit toml schemas for each object definition in objects.toml.

@jesseditson
Copy link
Owner Author

TOML schemas are not widely supported, however, Even Better TOML (and many/most other editors) support toml schemas via JSON schemas. These are in turn supported by taplo.

We should be able to use the inheritance order as per https://taplo.tamasfe.dev/configuration/using-schemas.html#using-schemas to provide autocomplete in most editors.

@jesseditson
Copy link
Owner Author

It probably makes the most sense to provide these schemas via a VSCode extension for archival

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant