-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Bug: [no-unnecessary-type-conversion] shouldn't have fixable property #11192
Copy link
Copy link
Closed
Labels
accepting prsGo ahead, send a pull request that resolves this issueGo ahead, send a pull request that resolves this issuebugSomething isn't workingSomething isn't workinglocked due to agePlease open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.Please 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-pluginIssues related to @typescript-eslint/eslint-plugin
Metadata
Metadata
Assignees
Labels
accepting prsGo ahead, send a pull request that resolves this issueGo ahead, send a pull request that resolves this issuebugSomething isn't workingSomething isn't workinglocked due to agePlease open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.Please 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-pluginIssues related to @typescript-eslint/eslint-plugin
Before You File a Bug Report Please Confirm You Have Done The Following...
Same as issue #10988.
Rule no-unnecessary-type-conversion has
fixable: 'code'andhasSuggestions: trueproperties inmetaat line31:But each fix is located in a
suggestproperty on line84,89,127,140,179,184,218,223,279,284,217and322:example on line
81:Based on
eslintdocumentation :Since fixable means "automatic fix" with --fix I suppose fixable is no more needed in this rule.