You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Decorators always transformed regardless of target #18713
So I need to wait for the new decorators proposal to be implemented?
yes
Which is probably going to disrupt a lot of Angular code that depends on legacy decorators.
We hope the roll-out will be coordinated with the Angular team to make sure the decorators can handle both versions of the proposal so only user-defined decorators would need to change.
There's a legacy decorators Babel transform I intend to use here. I don't think it would break anything if you just output the decorators as they appear in the source, for esnext.
It is not only the transforms, the decorator implementation as it stands today can not be labeled esNext. once we implement the new proposal we can safely label it as such.
Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.
Activity
mhegazy commentedon Sep 25, 2017
duplicate of #16882
mhegazy commentedon Sep 25, 2017
yes
We hope the roll-out will be coordinated with the Angular team to make sure the decorators can handle both versions of the proposal so only user-defined decorators would need to change.
It is not only the transforms, the decorator implementation as it stands today can not be labeled
esNext. once we implement the new proposal we can safely label it as such.mhegazy commentedon Oct 9, 2017
Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.