This definitely seems reasonable to check all imports.

I think the following would be good as a new selector: import.
Probably best to check both import namespace and import default.

Probably best to check both import namespace and import default.

I don't think it's a good idea to check default imports, because it is most likely that there will be no single rule for all default imports. In some cases, you will need PascalCase (classes) and in some cases you will need camelCase (functions).

I would say the same about namespace imports. I think for the most part, the name of the thing depends on the name of the module you're importing.

For example, a lot of our modules names are strictCamelCase, so we import namespaces as such, but at FB it's a react codebase, so you have a lot of PascalCase files (and import namespace as such).

We can always use the modifier to distinguish between namespace and default should you want to apply different formatting to both.

Also worth noting that you can apply multiple format options to a selector if you want to allow either. This mostly just means you can ban unnderscores or consecutive capitals.

We can always use the modifier to distinguish between namespace and default should you want to apply different formatting to both.

If it will be possible to distinguish between default imports and namespaces, then no problem. Thanks!

For default import there's already a PR to eslint-plugin-import for the rule which enforces naming the import the same as export. I could also imagine somebody could want to name the default import after the filename, but that's also a better fit for eslint-plugin-import. I don't see any other reason for linting names of default imports, unless you actually want to always rename them, which is weird.

Revisiting this - I'm not sure if it 100% makes sense for this to exist in the naming-convention rule.

On the one hand - it's trivial to add this to the rule, and you can validate that the name adheres to a format.

On the other hand - IMO the name of an import should be directly related to the thing being imported. I.e. it should be the filename (import * as foo from './foo', import foo from './foo').
This logic is not really possible to add to the rule itself.

Is there enough value in just ensuring the import name matches a format?

Is there enough value in just ensuring the import name matches a format?

I think yes, because this

IMO the name of an import should be directly related to the thing being imported. I.e. it should be the filename

is very opinionated (although I support this viewpoint) and in some teams the naming style may differ.