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
Following #3482 & coming over from typescript-eslint/typescript-eslint#6760: typescript-eslint is soon going to release a new v6 major version with reworked configurations. You can read up on it here: typescript-eslint.io/blog/announcing-typescript-eslint-v6-beta
Specifically, the configurations are reworked so that the recommended equivalents to what trpc uses now are:
'plugin:@typescript-eslint/recommended-type-checked'
'plugin:@typescript-eslint/stylistic-type-checked'
I can send a PR updating to them!
I suppose trpc could stay on typescript-eslint@v5, or use its own bespoke lint configs... neither option seems very appealing to me. 😄
No response
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the feature you'd like to request
Following #3482 & coming over from typescript-eslint/typescript-eslint#6760: typescript-eslint is soon going to release a new v6 major version with reworked configurations. You can read up on it here: typescript-eslint.io/blog/announcing-typescript-eslint-v6-beta
Specifically, the configurations are reworked so that the recommended equivalents to what trpc uses now are:
'plugin:@typescript-eslint/recommended-type-checked'
'plugin:@typescript-eslint/stylistic-type-checked'
Describe the solution you'd like to see
I can send a PR updating to them!
Describe alternate solutions
I suppose trpc could stay on typescript-eslint@v5, or use its own bespoke lint configs... neither option seems very appealing to me. 😄
Additional information
No response
👨👧👦 Contributing
Funding
The text was updated successfully, but these errors were encountered: