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
Consider adding meta.schema #7608
Comments
Sounds good 👍🏼 Maybe one downside is increasing a dependency that processes the JSON schema, right? |
Yeah, I believe ESLint uses Ajv JSON schema validator for this. |
Great. $ npm ls ajv
stylelint@16.3.1 /Users/masafumi.koba/git/stylelint/stylelint
├─┬ eslint@8.57.0
│ ├─┬ @eslint/eslintrc@2.1.4
│ │ └── ajv@6.12.6 deduped
│ └── ajv@6.12.6
└─┬ table@6.8.2
└── ajv@8.12.0 |
@MrHBS If you're interested, could you please show more specific idea to implement this feature so that others could image it easily? |
Sure. Here is an example of the schema of the And you can see here how ESLint validates the rule based on its schema. Finally, an example of tools that utilize this schema: eslint-doc-generator and eslint-typegen. |
@MrHBS Thanks for the helpful info. @ota-meshi Do you have any ideas to bring this feature from ESLint? |
Here's another use case for autocompletion: knowing the message arguments' names and positions. |
It would be equivalent to ESLint’s meta.schema. This can be used for generating plugin/rule documentation websites and typegens.
The text was updated successfully, but these errors were encountered: