fix(eslint-plugin): [no-unsafe-return] allow returning anything if explicitly returning any #7708
Conversation
…plicitly returning any
|
Thanks for the PR, @Josh-Cena! 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 failed.
|
| function foo(): any { | ||
| return [] as any[]; | ||
| } | ||
| `, |
There was a problem hiding this comment.
[Testing] Could you add a test for unknown too?
some room for interpretation.
Yeah I think this is fine as-is for now. If folks really give solid use-cases for the more complex ones we can always look into adding more complexity.
PR Checklist
any#3549Overview
I'm not sure if we should handle the following case:
const x: () => any = () => [] as any[];Overall the docs does not make it clear which cases are exempted, so I guess we have some room for interpretation.