docs(eslint-plugin): [no-explicit-any] add alternatives #11199
Conversation
|
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. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| ## Alternatives to `any` | ||
|
|
||
| Which type(s) to use instead of `any` depends on the context. | ||
|
|
There was a problem hiding this comment.
I can't find references of other non-straightforward scenarios to add... are there others we should mention?
|
View your CI Pipeline Execution ↗ for commit e90b396.
☁️ Nx Cloud last updated this comment at |
| ## Alternatives to `any` | ||
|
|
||
| Which type(s) to use instead of `any` depends on the context. | ||
|
|
There was a problem hiding this comment.
TODO: Add more straightforward cases from earlier in the file...
- If the type is known, describing it in an
interfaceortype- Mention
[i: string]/etc. index signatures too, either inside or alongside
- Mention
- If the type is not known, using the safer
unknowntype
PR Checklist
anyalternatives with no-explicit-any #11063Overview