This repository has been archived by the owner on Mar 29, 2024. It is now read-only.
Mark imported config #19
Labels
enhancement
New feature or request
Comments
I am trying to push that direction: eslint/eslint#18231 The config-viewer gets the data from runtime, so we can't possibly know the source for each config. That would require configs to provide the name properly later. |
configs.recommended[ESLint Config Viewer] Config payload
Data example "constructor-super": {
"type": "problem",
"docs": {
"description": "Require `super()` calls in constructors",
"recommended": true,
"url": "https://eslint.org/docs/latest/rules/constructor-super"
},
"name": "constructor-super",
"plugin": "eslint"
}, It would be helpful to mark rules with |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Clear and concise description of the problem
Use a reference instead of
anonymous #1
e.g.js.configs.recommended,
or@eslint/js.configs.recommended,
It would be useful to mark rules that are imported e.g.
js.configs.recommended
so that they can be differentiated from the manually addedrules
.Suggested solution
as above
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: