Import renaming for components with the same name not working on NgModule

[filipesilva]

I'm submitting a ... (check one with "x")

[x] bug report

Current behavior
If you have 2 components with the same name (but with different selectors etc), import by renaming the export and add them to the declaration array of an NgModule, only the first one is rendered.

Expected/desired behavior
Both components should be rendered on the app.

Reproduction of the problem
http://plnkr.co/edit/LxH6fzJ08GfwVYLz9y2A?p=preview
Switch order of GoodHeroComponent and EvilHeroComponent to see the bug (only the first is displayed).

What is the motivation / use case for changing the behavior?
A user should be able to rename imports and use components with the same class name.

Please tell us about your environment:

• Angular version: 2.0.0-rc.5
• Browser: Chrome 52
• Language: TypeScript 1.8

/cc @IgorMinar

[IgorMinar]

This is similar to the problem described in #10618 except that we are not minifying anything - the name collision is instead caused by SystemJS transpiling the imports and specifically transpiling the imports with symbol renaming.

[filipesilva]

@IgorMinar I just now tried this code on the quickstart, which transpiles via tsc instead of SystemJS, and the results were the same.

Also tried on angular-cli, which uses TS2.0 transpilation and no SystemJS at all, and also got the same results.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}