fix(routing): don't attach locals to request #12647
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.
Changes
This PR refactors how we internally handle the
locals
. The use of the symbol onRequest
has been limited only to the dev server, because that's the only way for adapters to send uslocals
in dev.Technically, this isn't a breaking change for the adapters because the
App.render
function already provides the APIs for passing initial locals. Plus, theRenderContext
class already holds the locals when it's created, so it's safe to remove the places whereReflect.set
/Reflect.get
is used.The only place where we need to keep the
Request
usage is a runtime, public API calledcreateContext
, which is only used my the edge middleware.Testing
The CI should pass
Docs
N/A