Added allow and forbid options to no-namespace rule

[el-angel]

I've added allow and forbid options, so this rule can be used for certain namespaces, instead for all

[coveralls]

Coverage increased (+0.006%) to 97.803% when pulling 86793f5 on el-angel:master into efd6be1 on benmosher:master.

[coveralls]

Coverage increased (+0.006%) to 97.803% when pulling 86793f5 on el-angel:master into efd6be1 on benmosher:master.

[coveralls]

Coverage increased (+0.006%) to 97.803% when pulling 86793f5 on el-angel:master into efd6be1 on benmosher:master.

[ljharb]

i assume this should cover specifiers, not the binding names?

(having the binding name and the specifier be the same in most of the examples make it unclear to which this applies)

[el-angel]

the allow option works as follows:

// { allow: ['myModule', 'React'] }
import * as React from 'react';
import * as myModule from '../module/randomFile.js';

[ljharb]

Also, can you elaborate on the use case here?

[el-angel]

Use cases would be there you want to force certain namespaces, and forbid others. This rule would make it very easy to force consistency and allow:

// { allow: ['constants'] }
import * as constants from '../constants.js;

while it would disallow:
import * as C from '../constants.js
for example.

Also you could make it possible to only disallow:

// { forbid: ['React'] }
import * as React from 'react';

while allowing all other namespace imports

[ljharb]

I'm not clear tho on why you'd want any path to be imported as constants?

It seems more like what you want is to point to a specific file, and allow that one to be imported as a namespace with a specific name?