fix: rename typeParameters to typeArguments where needed #5384
Thanks for the PR, @JoshuaKGoldberg!
typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.
The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.
🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings.
Thinking about this in terms of the broader ecosystem and the impacts - I wonder if we want to give consumers one major version to migrate?
How about this: this version we add the new property and we mark the old property as
If we wanted we could also do something like define a getter that throws when in a test environment to help flag plugins that they should migrate.
Additional details and impacted files
@@ Coverage Diff @@ ## v6 #5384 +/- ## ======================================= Coverage 87.06% 87.06% ======================================= Files 365 365 Lines 12579 12579 Branches 3720 3720 ======================================= Hits 10952 10952 Misses 1278 1278 Partials 349 349
Flags with carried forward coverage won't be shown. Click here to find out more.