Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flattening or elliminating/ignoring duplicate typings? #6305

Closed
ffMathy opened this issue Dec 31, 2015 · 2 comments
Closed

Flattening or elliminating/ignoring duplicate typings? #6305

ffMathy opened this issue Dec 31, 2015 · 2 comments
Labels
Duplicate An existing issue was already created

Comments

@ffMathy
Copy link

ffMathy commented Dec 31, 2015

Hi. Please see the question I have made here for a description of the problem.

http://stackoverflow.com/questions/34546446/flattening-typescript-typings-or-interfaces

Here's the post:

As a TypeScript developer, I have become too used to "Duplicate identifier" issues when working with .d.ts files.

Most recently, this occurred because I needed both the typings (.d.ts files) of Angular 2, and Parse.

Angular 2 doesn't distribute their .d.ts files through DefinitelyTyped, so I had to fetch Angular 2 through NPM which includes the source files as well.

Now, Parse's .d.ts come from DefinitelyTyped. Fine - so far, so good.

The issue then arises because both of these libraries depend on Node JS typings. The Node JS typings of Parse are located in the typings folder, whereas the Node JS typings of Angular 2 are located in a subfolder under node_modules/angular2.

This gives me a huge amount of duplicate identifier issues when compiling.

So, the big question(s)

- Can I flatten `.d.ts` files so that it doesn't have duplicates somehow? - Can I somehow make the TypeScript compiler ignore duplicate interface definitions?
@ffMathy
Copy link
Author

ffMathy commented Dec 31, 2015

I believe this is the biggest issue with TypeScript right now.

@kitsonk
Copy link
Contributor

kitsonk commented Dec 31, 2015

This is essentially duplicate, will be resolved by #4433.

@mhegazy mhegazy added the Duplicate An existing issue was already created label Jan 7, 2016
@mhegazy mhegazy closed this as completed Jan 7, 2016
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

3 participants