Decoupling: Consistent code location of story locking feature

Task Description

In the editor we moved all story locking (postLock) functionality to wp-story-editor. But there are still some references to postLock in story-editor.

In the dashboard, all story locking functionality is still in dashboard, not in wp-dashboard as one would expect.

Should we move that to wp-dashboard?

Or should we move everything to the “core” packages?

[sayedtaqui]

Oh, I wasn’t aware that the dashboard has story locking functionality too. Thanks for creating an issue for it. I will work on moving it to wp-dashboard and story-editor locking references.

[sayedtaqui]

Initially, moving the “Someone else is already editing this story” to the core editor looked like a good idea, but when I actually started moving, it didn’t feel worthwhile.

1. If I move PostLock to story-editor and use it in wp-story-editor and pass the props to enable “Take Over” functionality, I end up moving almost everything to achieve that.
2. If I move only PostLockDialog to story-editor for the sake of keeping the UI in the core editor, we anyways have to pass dialogContent and “Take Over” button from wp-story-editor and it doesn’t feel worthy to only keep such a small component in the core.

May its a wontfix.