fix: store fetchEvent in h3 context #1586
Merged
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
getFetchEvent
is flaky, creating & storing multiplefetchEvents
perh3Event
. The reason for this is vinxi duplicating the code including thefetchEventSymbol
per router (nksaraf/vinxi#51), e.g. if you console.log the symbolsolid-start/packages/start/src/server/fetchEvent.ts
Line 16 in 23b01da
Object.getOwnPropertySymbols(h3Event)
ingetFetchEvent
you get[ Symbol(fetchEvent), Symbol(fetchEvent) ]
on requests that affect multiple vinxi routers.What is the new behavior?
getFetchEvent
will maximally create onefetchEvent
perh3Event
by storing thefetchEvent
inh3Event.context
.h3Event
is stable across multiple routers andh3Event.context
is specifically made for situations like this as @pi0 already confirmed in an other thread (#1203 (comment)).