Skip to content

no-duplicate-imports rule triggered by import type statements #599

Closed
@Gozala

Description

Forking #592 to it's separate issue:

Standard uses 'no-duplicate-imports' rule which is triggered if there are two or more import statements from the same module.

It seems that this rule is also triggered for import type Flow statements, e.g. this results in an error:

import { foo } from 'someModule';
import type { Bar } from 'someModule';

There is no other way to combine these two statements into one import statement as flow want's to distinguish type and value imports.

I would really like this issue to be resolved to be able to use standard style with flow typed project.

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions