import styling rule

[trodi]

There doesn't appear to be a way to set a style on naming imported modules similar to how you can set the style of variable names. This may be an extension of an existing rule instead of an all together new rule.

If I have the following two imports, I'd like to check to see if they are in camelCase for example.

import * as Q from "q";
import * as Path from "path";

I'd expect the following "Foo" likely not to be affected by the naming convention.

import { Foo } from "foo";

In considering this, I referenced variable-name rule as a comparison.

"variable-name": [true, "ban-keywords", "check-format", "allow-leading-underscore"],

[jkillian]

Isn't the format of module names more semantic than syntactic though?

For example:

import * as Cat from "cat";
import * as path from "path";

const myCat = new Cat();
const somePath = path.resolve("some/path");

In other words, wouldn't you name your imported modules based off of how they are used?

[trodi]

Potentially, though I see value in being able to distinguish a given item was imported instead of created locally. Similar to the value you get from a naming convention distinguishing private members/functions versus public ones (which you might find in a checkstyle rule configuration).

[JoshuaKGoldberg]

@trodi this is covered by tslint-microsoft-contrib's import-name rule. This issue is really a subset of #1142 for determining which rules should be ported over.