8000 Bug: [use-unknown-in-catch-callback-variable] shouldn't have `fixable` property · Issue #10988 · typescript-eslint/typescript-eslint · GitHub
[go: up one dir, main page]

Skip to content
Bug: [use-unknown-in-catch-callback-variable] shouldn't have fixable property #10988
Closed
@mho22

Description

@mho22

Before You File a Bug Report Please Confirm You Have Done The Following...

  • I have tried restarting my IDE and the issue persists.
  • I have updated to the latest version of the packages.
  • I have searched for related issues and found none that matched my issue.
  • I have read the FAQ and my problem is not listed.

Rule use-unknown-in-catch-callback-variable has fixable: 'code' and hasSuggestions: true properties in meta on line 39 :

    fixable: 'code',
    hasSuggestions: true,

But each fix is located in a suggest property on line 175, 198, 224, 227 and 238 :

example on line `198 :

suggest: [
    {
        messageId: 'wrongTypeAnnotationSuggestion',
        fix: (fixer: TSESLint.RuleFixer): TSESLint.RuleFix =>
            fixer.replaceText(catchVariableTypeAnnotation, ': unknown'),
    },
],

Based on eslint documentation :

fixable: (string) Either "code" or "whitespace" if the --fix option on the command line automatically fixes problems reported by the rule.

Since fixable means "automatic fix" with --fix I suppose fixable is no more needed in this rule. Right ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issuebugSomething isn't workinggood first issueGood for newcomerslocked due to agePlease open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.package: 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

      0