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
As #22980 has pointed out. There is a sound logic for lossing decorators in declaration file ".d.ts".
But in my opinion, some decorators do provide useful information for readers. For example:
@expose({name: "sockFile", since: 2.0}) domainSocketFile: string
It tells me that when serialize to JSON, it will be renamed to "sockFile", and it will only be serialized after version 2.0
I'd suggest keepDecorators: never = default keepDecorators: declaration = put decorator in .d.ts files. Perhaps in comments?
keepDecorators: never
keepDecorators: declaration
The text was updated successfully, but these errors were encountered:
I think "design time decorator" #2900 can fit my need.
Sorry, something went wrong.
No branches or pull requests
As #22980 has pointed out. There is a sound logic for lossing decorators in declaration file ".d.ts".
But in my opinion, some decorators do provide useful information for readers. For example:
It tells me that when serialize to JSON, it will be renamed to "sockFile", and it will only be serialized after version 2.0
Suggestion
I'd suggest
keepDecorators: never
= defaultkeepDecorators: declaration
= put decorator in .d.ts files. Perhaps in comments?The text was updated successfully, but these errors were encountered: