-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Real-time collaboration: Disable syncing for "synthetic" template posts #73526
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
Conversation
|
Size Change: -2 B (0%) Total Size: 2.54 MB
ℹ️ View Unchanged
|
2fa222f to
fd0a051
Compare
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
ellatrix
left a comment
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.
Sounds good. Checking for the numeric ID will allow user created templates to synced when the template activation feature lands, because they are real entities, while still excluding registered/static templates. This is better than checking specifically for templates. 👍
What?
Disable syncing for "synthetic" template posts—meaning templates that do not map directly to an entity represented in the database.
Why?
When the "created template" experiment is enabled, activated templates are synthetically represented in the store with a string identifier and a
wp_idproperty pointing to the "real" entity record.These synthetic entities do not fulfill our expectations around how entities are handled by the store. Specifically, they are not handled by the
editEntityRecordandsaveEntityRecordactions incore-data. Therefore, they cannot be synced in the same way that "real" entity records are synced.How?
Do not sync entity record with non-numeric IDs.
Testing Instructions
Testing Instructions for Keyboard
No UI changes in this PR.