Support taplo with schemas

[dead10ck]

A couple of issues (#3383, #3897) have been opened around integration with taplo for TOML files related to Helix itself. It seems the root of this issue is that there are no schemas published for Helix.

I myself don't know much about how taplo works, or json schemas, but perhaps we could put together and publish a scheme, or maybe there's something we could check in and a default config setting we could use for them?

[ModProg]

For anyone interested in working on this, here is the documentation on how to create/publish schemas for taplo: https://taplo.tamasfe.dev/configuration/developing-schemas.html

[LukeHalasy]

I would love ❤️ to run with this.
Let's auto-generate the schema for helix-related TOML files as others have mentioned.

Additionally, we should commit the generated schema files since the possible keys + values within each TOML file change depending on the commit you are on.

Will be awesome to be able to view the documentation for all the possible keys within the TOML files without having to go to the book/website (especially for editing themes when you need to look up what every scope does).

(Would be a cool UX feature to have Taplo auto-installed along with helix so that anytime a new user goes to their config they have auto-complete enabled by default)

[ModProg]

Additionally, we should commit the generated schema files since the possible keys + values within each TOML file change depending on the commit you are on.

It should probably be possible for helix to tell taplo exactly what schema to use, so you always have the correct completions.

Publishing them to the Json Schema Store additionally makes sense, but I think it is save to assume that the config file you are editing is in most cases for the version of helix you are currently running.

[pascalkuthe]

I don't really think it makes sense to invest a bunch of effort into writing and maintaining these schemas at this point since we plan to replace the toml config with a scheme based config in the future

[LukeHalasy]

I don't really think it makes sense to invest a bunch of effort into writing and maintaining these schemas at this point since we plan to replace the toml config with a scheme based config in the future

Thanks for the quick notice. I will NOT be running with this then.

Should we close this issue since the original description talks about "integration with taplo for TOML files related to Helix itself" and we are going to be moving away from TOML-based configs ?

[the-mikedavis]

Yep, let's close this out since we're eventually planning on switching away from TOML

[andradei]

What is Helix switching to?

[the-mikedavis]

The plugin system will most likely be a scheme dialect, so config will be written in scheme and be scriptable rather than TOML

[1mjw]

keep both options; you are ruining a beautiful thing by eliminating TOML