-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Feature suggestion: Optionally emit property names #33197
Comments
|
With recent changes to the proposal (see #27644) that would be standard behavior (with |
As @ark120202 points out, at this point, this is basically a duplicate of #27644, since the new property emit will be something like |
This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes. |
1 similar comment
This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes. |
This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes. |
Hello Team,
I've created a lot of generic solutions with TypeScript but always struggled with this one. Is there a way to get all properties defined in TypeScript, but at runtime. For Example
class Car { name: string; }
will compile to
var Car = /** @class */ (function () { function Car() { } return Car; }());
Could there be a compiler option which would emit
var Car = /** @class */ (function () { function Car() { this.name = null; } return Car; }());
This would allow us to create better generic solutions with Typescript. I searched a lot and maybe used the wrong search terms, but I could not find a solution to this.
The text was updated successfully, but these errors were encountered: