Skip to content

require-description - Allow comment above #190

@fregante

Description

@fregante

For longer rule names, I prefer placing the comment on top so it doesn't get lost. e.g.

// eslint-disable-next-line @typescript-eslint/no-non-null-assertion, @typescript-eslint/no-unnecessary-type-assertion -- The build fails if this is undefined, so `!` is appropriate

vs

// The build fails if this is undefined, so `!` is appropriate
// eslint-disable-next-line @typescript-eslint/no-non-null-assertion, @typescript-eslint/no-unnecessary-type-assertion

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions