Overview

One of the biggest user requests I see in the wild for typescript-eslint is banninganys from sneaking into the codebase. We have a suite of rules:

• @typescript-eslint/no-unsafe-argument
• @typescript-eslint/no-unsafe-assignment
• @typescript-eslint/no-unsafe-call
• @typescript-eslint/no-unsafe-member-access
• @typescript-eslint/no-unsafe-return

I'd like to write a blog post explaining:

1. Why you'd want to banany even withnoImplicitAny enabled
2. Whyunknown is a better alternative
3. How each of those rules helps