Skip to content
This repository has been archived by the owner on Jul 30, 2018. It is now read-only.

Non-native Symbol when targeting ES6 #149

Closed
kitsonk opened this issue Apr 21, 2016 · 1 comment
Closed

Non-native Symbol when targeting ES6 #149

kitsonk opened this issue Apr 21, 2016 · 1 comment
Labels
Milestone

Comments

@kitsonk
Copy link
Member

kitsonk commented Apr 21, 2016

TypeScript complains when using well known symbols that TypeScript cannot determine are from the global Symbol interface. (see microsoft/TypeScript#8169, microsoft/TypeScript#8099, microsoft/TypeScript#5579, microsoft/TypeScript#2012)

We need to provide a viable workaround for our Symbol shim due to this.

@kitsonk kitsonk self-assigned this Apr 21, 2016
@kitsonk kitsonk added the bug label Apr 21, 2016
@kitsonk kitsonk modified the milestones: 2016.04, 2016.05 Apr 21, 2016
@kitsonk kitsonk removed this from the 2016.05 milestone May 25, 2016
@kitsonk kitsonk added this to the 2016.06 milestone Jun 23, 2016
@kitsonk kitsonk modified the milestones: 2016.06, 2016.07 Jul 4, 2016
@kitsonk kitsonk modified the milestones: 2016.07, 2016.08 Aug 1, 2016
@kitsonk
Copy link
Member Author

kitsonk commented Oct 4, 2016

We have a typing that is loaded in ES5 environments that puts the Symbol in the global namespace. It could be improved when targeting ES6, but it works for now (and Symbol has moved to dojo-shim anyways) so closing...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant