JSON Schema for config.json

[Cianidos]

Please, add a JSON schema for the config.json file and incorporate a "$schema" annotation within the default configuration file to improve user experience via utilizing LSP capabilities. https://json-schema.org/understanding-json-schema/reference/schema
Thank you.

To upvote this issue, give it a thumbs up. See this list for the most upvoted issues.

[ericdallo]

thanks for the tip!

[ericdallo]

Docs udapated, schema available https://eca.dev/config.json

[Cianidos]

@ericdallo sorry, but there is an issue with current scheme...
I have such "doc" provided by lsp...

Available models for this provider\. Each key is the model alias\.

Something went wrong with encoding.

I have this lsp package.

~$ npm view -g vscode-langservers-extracted

vscode-langservers-extracted@4.10.0 | MIT | deps: 16 | versions: 23
HTML/CSS/JSON/ESLint language servers extracted from [vscode](https://github.com/Microsoft/vscode).
https://github.com/hrsh7th/vscode-langservers-extracted#readme

GNU Emacs 30.2 (build 2, x86_64-pc-linux-gnu, X toolkit, cairo version 1.18.2, Xaw scroll bars) of 2025-12-26
and eglot

    Package: eglot
     Source: Straight
     Pinned: f110d26e0356983d07d94d38a1b384a0f79b6b8c
      Build: HEAD -> master, replaced f110d26 2026-01-06 00:07:04 +0000

[ericdallo]

@Cianidos did a improvement adding markdownDescription, not sure it will fix it, it seems to be a lsp server issue if not.

[Cianidos]

Now the schema (LSP docs) looks perfect, thank you @ericdallo !
I haven’t tried the cutting edge of ECA. Please consider updating the default config.json template to add "$schema": "https://eca.dev/config.json" if it isn’t already included.

[Cianidos]

Or even make the ECA config "well known" by adding it to public repos like https://www.schemastore.org/. I'm not sure what the actual "default" repo is, but if it works "magically," it would be great for users.

[ericdallo]

thanks, will do!

[ericdallo]

Done here