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
Now that decorators proposal comes to stage 3, we should watch on it. It will eventually become standard and seems can solve our performance problem introduced from legacy decorator model.
Once we adopt the new specification, can we ensure the full-compatibility? I'm afraid not. The model has changed and we should consider on users' wrapping-invocation.
How about the legacy decorators written by users themself.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Now that decorators proposal comes to stage 3, we should watch on it. It will eventually become standard and seems can solve our performance problem introduced from legacy decorator model.
What we should watch:
Decorator proposal status: https://github.com/tc39/proposal-decorators
Babel's implementation status:
TypeScript's implementation status:
What we should concern:
The decorator model and performance.
Migration.
Once we adopt the new specification, can we ensure the full-compatibility? I'm afraid not. The model has changed and we should consider on users' wrapping-invocation.
How about the legacy decorators written by users themself.
Beta Was this translation helpful? Give feedback.
All reactions