Skip to content

[ban-ts-comment] Enforce @ts-expect-error: TS1234 because xyz #4253

Closed
@fregante

Description

@fregante

Feature request

I use ban-ts-comment with ts-expect-error so I must include a description every time, which is great!

// @ts-expect-error The initial types were incorrect

but every time I encounter this it's not very actionable because I don't know what error it's expecting. I think it should always include the exact error ID:

// @ts-expect-error TS2717 The initial types were incorrect

Could this be an option?

{
	'ts-expect-error': 'allow-with-description-and-id',
	minimumDescriptionLength: 10,
}

Versions

package version
@typescript-eslint/eslint-plugin 5.5.0
TypeScript 4.5.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issueenhancement: plugin rule optionNew rule option for an existing eslint-plugin rulepackage: eslint-pluginIssues related to @typescript-eslint/eslint-plugin

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions