[Fix] no-named-default: ignore Flow import type and typeof

[christianvuerings]

Description

Syncs the behavior of no-named-default with named, which also ignores Flow imports & exports:

Note that type imports and exports, as used by [Flow], are always ignored.

Without this fix, no-named-default conflicts with the flowtype/type-import-style rule with a default setting of "identifier".

Issue

"Identifier syntax":

// @flow
import { type default as Foo } from "./bar";

Gives following error:

2:15  error    Use default import syntax to import './bar'.       import/no-named-default

Whilst the "declaration syntax":

// @flow
import type Foo from './bar';

Generates no error.

Related PRs / Issues

• Fix named flow type imports in specifiers. #1117: Fix named flow type imports in specifiers (import/named doesn't ignore Flow identifier syntax type import #1115)
• [fix] named: ignore Flow import typeof and export type #1345: [fix] named: ignore Flow import typeof and export type

[coveralls]

Coverage increased (+1.9%) to 71.388% when pulling 4c92c47 on christianvuerings:no-named-default-flow into a45661b on benmosher:master.

[ljharb]

Seems reasonable, thanks!

(btw, nice work on getting the changelog, tests, and commit message conventions nearly perfect on your first PR!)

[christianvuerings]

@ljharb Thanks for the quick merge!

Do you know when we could release the next version of eslint-plugin-import? We would love to use this fix in our codebase and avoid pulling in a specific commit.

[ljharb]

@christianvuerings there's no planned timeline. generally it's a few months between releases, so we're coming due for one.

[christianvuerings]

@christianvuerings there's no planned timeline. generally it's a few months between releases, so we're coming due for one.

@ljharb should I follow the steps in RELEASE.md to get a release cut? I can do everything until step 4.

[ljharb]

@christianvuerings no, master’s broken right now. See #1986.