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

Transpiler should error if a static property is declared that the language already defines. #2462

Closed
reppners opened this issue Mar 23, 2015 · 2 comments
Labels
By Design Deprecated - use "Working as Intended" or "Design Limitation" instead

Comments

@reppners
Copy link

Based on this issue:

Can the transpiler warn you if something like this happens?

@qc00
Copy link

qc00 commented Mar 23, 2015

Since lib.d.ts is generated from IE definitions, I guess it's entirely possible that the compiler is not even aware there's a name property.

The interesting question is, once it has been added per ES6, how should the compiler handle unwritable properties in general? Would getters/setters be added to interfaces?

@mhegazy mhegazy added the By Design Deprecated - use "Working as Intended" or "Design Limitation" instead label Mar 24, 2015
@mhegazy mhegazy closed this as completed Mar 24, 2015
@mhegazy
Copy link
Contributor

mhegazy commented Mar 24, 2015

@billccn is correct the name declaration is comming from lib.d.ts, and you can edit the file to remove the definition. Also see #1351 for removing these properties from the library file.

@microsoft microsoft locked and limited conversation to collaborators Jun 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
By Design Deprecated - use "Working as Intended" or "Design Limitation" instead
Projects
None yet
Development

No branches or pull requests

3 participants