fix: treat kj::Array(Ptr)<const char>
s as TypeScript string
s
#1820
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.
Hey! 👋 This PR ensures
kj::Array(Ptr)<const char>
s are treated asstring
s when generating TypeScript types.Previously we assumed both
char
s andunsigned char
s were byte arrays. This isn't quite right,kj::byte
is defined asunsigned char
andchar
arrays representstring
s in JSG. This PR updates the TypeScript generator to only treatunsigned char
arrays as byte arrays.This results in the following diff for the
experimental
entrypoint (all compatibility flags enabled) from@cloudflare/[email protected]
(the last correct types version) to the types with this change:Diff
Fixes #1818