TypeScript codegen backend #8118
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #6196 (comment) for context.
I tried to implement all the features we need, including those not supported by genType today.
Currently, it is somewhat complex to support both
.tsand.d.tsoutputs. Eventually, it could simplify the codegen process by unifying the codebase after deprecating genType and by organizing the context and config structures.Config
For dts:
{ "sources": "src", "package-specs": [ { "module": "esmodule", "in-source": true, + "dts": true } ] }For TypeScript
(config schema would be changed)
{ "sources": "src", + "language": "typescript", "package-specs": [ { "module": "esmodule", "in-source": true } ] }Attributes
@as: Rename the generated types.@external("TypeName"): Use external (global) type@external(("package-name", "Name", true)): named type import@external(("package-name", "default", true)): default import as type@external(("package-name", "*", true)): namespace import as type@opaque: Force the type to be opaque