-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Add compiler options to disable decorator transform #16882
Comments
It will be possible once we implement the new decorators proposal using |
Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed. |
@mhegazy I noticed this was automatically closed just now but I think it is worth considering a dedicated flag for this assuming that metadata emit is something that will be supported in some form by the new implementation. This would mean that TypeScript and Babel will continue to have very different behaviors. Currently, using On the other hand, if metadata emit is actually dropped then it does make sense to control this with |
Once we implement the new proposal it becomes an esNext feature, it will be passed thorough in esNext and transfomred otherwise. currently the semantics are different, so the compiler would tell something that does not match what babel would transform. |
metadata is a different issue. it will be transformed as a decorator in |
That seems very elegant and addresses all of my concerns. Thank you for explaining. |
Please reopen this issue, since #18713 is labeled duplicate with this. |
As explained in this issue and the other issue, this is intended behaviour. Therefore this issue is closed. |
We missing an option to disable decorator transform. Code below
preserveDecorators
option is virtual.TypeScript Version: 2.4.0
Code
tsconfig.json
index.ts
Expected behavior:
index.js
Actual behavior:
index.js
The text was updated successfully, but these errors were encountered: