-
-
Notifications
You must be signed in to change notification settings - Fork 272
Description
A common setting in typescript is to have noImplicitAny: true in your tsconfig to enforce stricter typescript usage together with the plugin:@typescript-eslint/recommended and plugin:@typescript-eslint/strict eslint plugins.
However the generated models may sometimes correctly consist of explicit any(s) which currently results in the error:
Unexpected any. Specify a different type. eslint(@typescript-eslint/no-explicit-any)
Previously the generated files had eslint-disable in the top of them but that is no longer the case and eslint is now used to format/lint the output so can no longer be disabled/ignored safely.
How should this be handled?
Theres the same issue with
Unexpected class with only static properties. eslint(@typescript-eslint/no-extraneous-class)
in the generated services.
This can be observed in the previous reproduction repo i shared with @jordanshatford as well.