Skip to content
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

feat: Use typescript-eslint@v6 & its reworked configs #4540

Closed
1 task done
JoshuaKGoldberg opened this issue Jun 19, 2023 · 0 comments · Fixed by #4541
Closed
1 task done

feat: Use typescript-eslint@v6 & its reworked configs #4540

JoshuaKGoldberg opened this issue Jun 19, 2023 · 0 comments · Fixed by #4541

Comments

@JoshuaKGoldberg
Copy link
Collaborator

JoshuaKGoldberg commented Jun 19, 2023

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

  • 🙋‍♂️ Yes, I'd be down to file a PR implementing this feature!

Funding

  • You can sponsor this specific effort via a Polar.sh pledge below
  • We receive the pledge once the issue is completed & verified
Fund with Polar
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant