Create no-global-assign rule

What version are you using?

2.2.0

What did you do?

I have the file test.js:

/*global a:false */
a = 5;

I have the configuration .eslintrc.yaml:

root: true
rules:
  no-undef: 2

I linted the file with the command-line argument eslint test.js.

What happened?

It did not report any errors.

What did you expect to happen?

I expect it to warn me that I am assigning to a global variable with the false flag, as described in the documentation.

[mikesherov]

Ok, yeah, I think we can mark this as JSHint compat though, no? And I won’t work on this until JSCS compat is done, but I would like to champion this, so when it gets 3 thumbs, I can assign it to myself?

[mikesherov]

ok, I’ll champion this. Important to maintain feature parity with JSHint here. I recommend:

1. Fixing docs for no-undef, and also have them point to this new rule.
2. Recognizing the \* global var:true *\ annotation as exceptions to this rule.
3. ignore \* global var:false *\ as that only applies to no-undef.
4. Also recognizing an array of exceptions to this rule.
5. Rule shall be named no-global-assign.

Given 2 & 4, a dev coming from JSHint SHOULD convert \* global var: true *\ to // eslint no-global-assign ["error", ["var"]] *\, but isn’t absolutely required to do so.