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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interactivity API: Refactor context proxies #64713
Interactivity API: Refactor context proxies #64713
Changes from all commits
3cfcda7
9853ca3
c40acbd
0f12399
8859cd5
dc16445
ad6a974
d09316d
2c17bf3
2392742
d11f743
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not clear to me that
deepMerge
is equivalent to theupdateContext()
function. Should it be equivalent or are we consciously changing the logic here? If it's the second one, then why do we do that?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea here is to use
deepMerge()
with theoverride
option set tofalse
. This algorithm follows the same logic asupdateContext
but does not manipulate the reactive object directly and only updates the signals created beforehand.That way, we avoid
wp-context
subscribing unnecessarily to the modified context and prevent wasteful signal instantiation. 🙂There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I see. Upon further inspection the logic does seem almost the same. The only 2 differences I see is:
We do not use
peek()
anymore. This I assume is because we the context is not wrapped in proxies anymore like you mentioned here.I see that we're now assigning empty object here:
gutenberg/packages/interactivity/src/proxies/state.ts
Lines 298 to 301 in ce56700
but previously we used to re-assign the property:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly. 🙂
That was wrong. We don't want to copy a plain object's reference from
source
when callingdeepMerge
.