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.

Thanks again!

🙏 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.

We should add a lint rule for this to warn against using the method directly.

Could expand this internal lint rule to cover it:

https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin-internal/src/rules/no-poorly-typed-ts-props.ts

TBD whether this original approach works, but it would also be nice to not use an internal TypeScript compiler API... I'd be interested in looking at that too.

Codecov Report

Merging #2567 into master will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2567      +/-   ##
==========================================
- Coverage   92.82%   92.82%   -0.01%     
==========================================
  Files         290      291       +1     
  Lines        9505     9514       +9     
  Branches     2664     2666       +2     
==========================================
+ Hits         8823     8831       +8     
  Misses        323      323              
- Partials      359      360       +1     

Flags with carried forward coverage won't be shown. Click here to find out more.