Name collision by module import in Angular 2 - is there a way to prevent it

angular typescript import name-collision
9ilsdx 9rvj 0lo picture 9ilsdx 9rvj 0lo · Nov 18, 2016 · Viewed 7.8k times · Source

I've almost caused a name collision, because I've created a class with common name Message, which already exists in PrimeNG:

import {Message} from "primeng/primeng";
import {Message} from "./dto";

Because it is my code, I could simply rename the class to anything else (like MessageDTO). But if this was the external class, I'd have an issue.

Is there any way to import class with alias, or any other mean to deal with name conflicts? I Java you can refer to class using fully qualified name instead of import, which looks ugly but is often unavoidable. How it looks like in Angular 2/TypeScript?

Answer

ranakrunal9 picture ranakrunal9 · Nov 18, 2016

As per TypeScript import document imports can also be renamed same as below :

import { Message } from "primeng/primeng";
import { Message as MessageDTO } from "./dto";

Related questions

How to use Angular2 and Typescript in Jsfiddle

Dummy question ... I try to code an angular2 (2.0.0-beta.6) app in Typescript in jsfiddle. I know that there is other solution online but ... In fact, my example is very small and the problem is on import module : import {bootstrap} from …

Read More
Importing Javascript library (jsencrypt) into Angular 2 app

I have looked through all the tutorials revolving around this issue, and havn't been able to find a solution. Some background first. I have a Angular 2 app and I need to use this JS library for encryption: https://github.com/…

Read More
Can't bind to 'ngModel' since it isn't a known property of 'input'

I've got the following error when launching my Angular app, even if the component is not displayed. I have to comment out the <input> so that my app works. zone.js:461 Unhandled Promise rejection: Template parse errors: Can't …

Read More