这是indexloc提供的服务,不要输入任何密码
Skip to content

How should noImplicitAny be handled? #382

@Darhagonable

Description

@Darhagonable

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug 🔥Something isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions