Allow post lock dialog to return and retain functionality#32
Conversation
|
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. |
|
Size Change: +19 B (0%) Total Size: 1.93 MB
ℹ️ View Unchanged
|
| return null; | ||
| } | ||
|
|
||
| if ( window.__experimentalEnableSync ) { |
There was a problem hiding this comment.
I'm trying to think about what this PR would look like when we want to get this into core. Would this change be accepted by the Gutenberg folks, given instead of doing window.<access flag here> they are adding a filter for plugin users? If it is accepted, what would it look like when we want to move it out of the experiment stage and have it be a core feature? How would null be returned then?
There was a problem hiding this comment.
I would imagine it being either similar to the isLocked check directly above. Currently the override just short-circuits any logic in here, so either way, it would require refactor.
There was a problem hiding this comment.
Could you add a todo about this? That way it's known and we have an idea of how to approach it?
What?
Directly overrides post lock modal and returns when in experimental sync (collaborative editing) mode.
Why?
In Automattic/vip-real-time-collaboration#6 we introduced a method to override the post lock modal, but this resulted in the functionality within the post lock modal being lost also.
How?
Returns early on setting check.
Testing Instructions