We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
TypeScript 5.0 fully supports stage 3 TC39 decorators.
The legacy decorators are still supported: https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#differences-with-experimental-legacy-decorators, but the new decorators have some advantages. For example, they work without a special flag, have better type-checking, etc.
Support the new TC39 decorators.
Please see TypeScript documentation.
Keep up with JS/TS evolution.
The text was updated successfully, but these errors were encountered:
we cannot have that for now due to the lack on parameter decorators.
Sorry, something went wrong.
Also no emitted decorator metadata support, which nest heavily uses
I don't think we'll support JS decorators till the metadata support & parameter decorators are implemented
No branches or pull requests
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
TypeScript 5.0 fully supports stage 3 TC39 decorators.
The legacy decorators are still supported: https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#differences-with-experimental-legacy-decorators, but the new decorators have some advantages. For example, they work without a special flag, have better type-checking, etc.
Describe the solution you'd like
Support the new TC39 decorators.
Teachability, documentation, adoption, migration strategy
Please see TypeScript documentation.
What is the motivation / use case for changing the behavior?
Keep up with JS/TS evolution.
The text was updated successfully, but these errors were encountered: