-
Notifications
You must be signed in to change notification settings - Fork 185
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
Make it an official proposal for ES (?) #9
Comments
Right now we're still working to finalize Decorators for ES2016. Until the Decorators proposal progresses to at least Stage 2, I don't want to complicate the discussion with this proposal. That said, this is very much on the minds of the Decorators champions and the working group responsible for moving Decorators forward. |
Thanks for the clarification! |
Decorators are now in Stage 2. https://github.com/tc39/proposals |
@MuYunyun The reflect object itself isn't introduced with this proposal. |
Thanks, I understand. I think the refect-metadate is a friendly api with decorate, is it? |
I opened tc39/proposal-decorators#225 last week because of concern that Decorators don't have any kind of reflection built in. I re discovered this spec by accident, and located this relevant ticket. I don't feel like I've gotten anyone at all interested though. :( :( :( |
Now that the Decorator Metadata is at Stage 3, it is unlikely that this proposal will be brought to committee. |
This is half question, half suggestion: Are there plans for adding
Reflect.metadata
to the list of ECMA262 proposals? It seems like there is progress in the TypeScript integration but no trace of adding it to JS proper. I think it would be valuable having it exposed early in that list because it could help direct the conversation about the decorator proposal (e.g. an official way of implementing annotations using decorators instead of just "random code patching/obfuscation").The text was updated successfully, but these errors were encountered: