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.
π Linked issue
β Type of change
π Description
Before releasing h3 1.8, this PR makes sure we minimize new interface changes and chances of future possible breaking changes.
Meanwhile, I was trying new Web APIs, and figured it is so easy to shoot in the foot by runtime expensive getters such as
event.url
orevent.request
(did myself ironically!). Composable utils are a little bit more verbose to use but also easy to replace or deprecate.Changes from the last RC:
event.rawBody
togetRequestWebStream(event)
event.request
totoWebRequest(event)
event.web?
(WebEventContext = { request, url }
)event._originalPath
internal getterevent._hasBody
internal getterevent.url
togetRequestURL(event)
readRawBody
andreadBody
to support web request body streamsgetRequestPath
to only normalize trailing double slashesgetRequestPath
to 1.7.1 implementation and deprecateπ Checklist