We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://eslint.org/blog/2022/08/new-config-system-part-2/
This would let us reuse rules by just changing names (I presume) instead of manually merging them each time, like:
eslint-config-pixiebrix/index.js
Lines 266 to 278 in 81e6a3e
This change would make the following change more reasonable:
import/no-restricted-paths
no-restricted-imports
eslint.org/docs/latest/use/configure/configuration-files-new Suggested in #176 (comment) I'm not sure if this is immediately possible due to our dependencies, but I can look into it if desired.
eslint.org/docs/latest/use/configure/configuration-files-new
Suggested in #176 (comment)
I'm not sure if this is immediately possible due to our dependencies, but I can look into it if desired.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://eslint.org/blog/2022/08/new-config-system-part-2/
This would let us reuse rules by just changing names (I presume) instead of manually merging them each time, like:
eslint-config-pixiebrix/index.js
Lines 266 to 278 in 81e6a3e
This change would make the following change more reasonable:
import/no-restricted-paths
withno-restricted-imports
#35The text was updated successfully, but these errors were encountered: