New rule: `no-reserved-imports` about eslint-plugin-ember HOT 9 OPEN

cc @Turbo87 ☝️

from eslint-plugin-ember.

You can already do this with ESLint with this rule:

'no-shadow': ['error', { 'builtinGlobals': true }]

from eslint-plugin-ember.

Oh, true @t-sauer. Then I think we should add this to recommended config.

from eslint-plugin-ember.

Then I think we should add this to recommended config.

that would require a breaking change release again and I'm very much against that in the foreseeable future. IMHO we should only do breaking change releases if we actually need to break how a rule behaves, the recommended config should ideally live outside of this repo/project.

from eslint-plugin-ember.

@t-sauer the potential advantage of having a custom rule would be that it can be --fix-able, but it's probably not worth it in this case 🤔

from eslint-plugin-ember.

I found that there was a similar suggestion made to the Airbnb eslint base and it was not merged, with this as the reasoning: airbnb/javascript#667 (comment)
So similarly, I don't think we should be including the builtinGlobals option in our configuration.

from eslint-plugin-ember.

I think that having a dedicated fixable rule just for the ember object, string, etc. might be a good idea, I'd personally find it valuable.

from eslint-plugin-ember.

Ok, so it looks like indeed having a dedicated rule will be most valuable in this case.

from eslint-plugin-ember.

Picking this up then - will probably make a PR around saturday/sunday

from eslint-plugin-ember.