correctly serialize headers and timeout #2071
Merged
+60
−29
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.
Description of Changes
Restrict the use of
HeadersInit
in aTransportEvent
orTransportError
to only permit jsonifiable members.Serialize timeout into the request header as in typical connectrpc.
Technically, an exported type becomes narrower, but the now-omitted member was invalid, and no external API has changed its accepted input/output formats.
Related Issue
@penumbra-zone/transport-dom
typeTransportEvent
permits a non-transferable field #2070@penumbra-zone/transport-dom
transport accepts timeout configuration but only uses it locally #2072Checklist Before Requesting Review