Thanks for the PR, @phaux!

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

Would it be possible to allow any, for codebases that are not yet fully typed?

Instead of options like allowBoolean or allowNumber, why not allow configuration like allowed: ['number', 'bigint', 'boolean', 'null']?

@glen-84 Noted.

@ckknight I was actually considering going into the other direction: allow "loose" option which enables all types which have obvious string representation, but later I split that into 3 separate options. Having 5 options is too much IMO. Also, I can't think of a case where you would want only one of number | bigint or null | undefined

@phaux I'm not sure how common it would be, but one advantage of using a more generic filter would be an ability to allow some application-specific types with expected toString implementation.

Codecov Report

Merging #850 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #850      +/-   ##
==========================================
+ Coverage   94.17%   94.22%   +0.05%     
==========================================
  Files         124      125       +1     
  Lines        5322     5371      +49     
  Branches     1492     1509      +17     
==========================================
+ Hits         5012     5061      +49     
  Misses        177      177              
  Partials      133      133