-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[WIP]: handle duplicated blocks from entities with aliases and entity management #27084
Conversation
Size Change: +1.24 kB (0%) Total Size: 1.22 MB
ℹ️ View Unchanged
|
99cb71d
to
9055bb7
Compare
9055bb7
to
2c2fec5
Compare
if ( actionsToIgnore.includes( action.type ) ) { | ||
return; | ||
} | ||
if ( action.clientId ) { |
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.
This one handles things like updating block attributes: the action might only affect one client ID, so just apply it to the other aliased client IDs too. This however probably doesn't work for any action that might have clientId but also a root client ID 🤔 Thankfully most of those use clientIds
.
superseded by #27885 Thanks for you work on these issues @noahtallen |
Description
This resolves #22639 by implementing the approach I described here: #24180 (comment).
TLDR:
This way, edits are up to date inside the block tree, and we only have incoming/outgoing changes happen once. No need to handle multiple syncs or any of that nonsense!
Tasks:
How has this been tested?
Screenshots
Types of changes
Checklist: