Closed
Description
Description
I would like to propose an extension to the existing consistent-type-imports
rule. This is linked to the work done in #4237
I think it would be beneficial for people who are interested in adopting the new inline type import syntax introduced in Typescript 4.5. We can introduce a flag, for example preferInlineTypeImports?: boolean
.
Like @bradzacher mentioned, it's tricky to do a fixer, so we don't need it for now, but at least a way to warn people about violation would be great.
Fail
import type { c } from './c';
import { a } from './a';
import type { b } from './a';
Pass
import type { c } from './c';
import { a, type b } from './a';
Let me know what you think about this. If you give me a green light, I think if I can try working on this feature.
nonoroazoro, shelimov, amanmahajan7, florian-ernst-alan, BennoDev and 50 moredzearing, service-paradis, nrgnrg, schickling, lensbart and 13 more
Metadata
Metadata
Assignees
Labels
Go ahead, send a pull request that resolves this issueGo ahead, send a pull request that resolves this issueNew rule option for an existing eslint-plugin ruleNew rule option for an existing eslint-plugin ruleIssues related to @typescript-eslint/eslint-pluginIssues related to @typescript-eslint/eslint-plugin