Namespaced global variables

I would like to solicit feedback about implications of adding this potential extension to the globals configuration.

What version are you using? 4.10.0

What problem do you want to solve? Create a configuration that will allow global variables to be defined dynamically using a namespace. This would allow a namespaced set of global variables that can be used within a context where no-undef is otherwise enforced.

What’s your take on the correct solution to problem? Allow for a configuration along the lines of:

{
  "globals": {
    "somename_": {
      "namespace": true,
      "prefix": true
    }
  }
}

And any global variables prefixed with somename_ would be allowed in files within which they are not declared.

[not-an-aardvark]

Sorry, I think I used the wrong message (edited my comment above). As you said, this probably would have needed to be a core change and not a custom rule.

[saschabratton]

Gotcha. Thanks again!