Can we have a separate error code for "Untyped decorator makes function ... untyped"
Feature
Can we have a separate error code for "Untyped decorator makes function ... untyped"?
Pitch
Many frameworks require the user to wrap their functions in decorators and many of these libraries does not have (good?) type annotations. When using such a framework you will get a lot of "Untyped decorator makes function ... untyped" errors. Currently the error code for that error is misc, which makes it awkward to disable it. If we gave these errors their own error code we could easily disable them in a configuration, making it more pleasant to use these libraries.
P.S.
I feel like these errors, along with no-untyped-call and no-any-return, belong to a class of errors that are errors-caused-by-poorly-annotated-third-party-libraries that we tend to get a lot of and are hard to fix in a principled way. Maybe we could have an easy way disable all of them?
This sounds reasonable to me, feel free to send a PR.
I'm generally supportive of making error codes more granular whenever there's a reasonable use case presented.