OT Frontend Changes - Stage 1 #298
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
Tests are failing because there appears to be something wrong with PIP implying the DB startup script couldn't be run and consequentially the backend testing env couldn't be created |
Varun-Sethu
force-pushed
the
varun/otFrontend/stage1
branch
from
37b6f36 to
ba6ee0f
Compare
Varun-Sethu
force-pushed
the
varun/otFrontend/stage1
branch
from
ba6ee0f to
88a69cc
Compare
lhjt
requested changes
Nov 1, 2022
Varun-Sethu
force-pushed
the
varun/otFrontend/stage1
branch
from
4688b16 to
f336dde
Compare
Varun-Sethu
force-pushed
the
varun/otFrontend/stage1
branch
from
f336dde to
5e9dcfc
Compare
lhjt
approved these changes
Nov 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR adds the first stage of the required changes to the front-end in order to support operational transform. This PR captures SlateJS operations and propagates them to a central place for delivery to the server. The PR after this will focus on translating SlateJS operations into the CMS operation format + sending them to the server and the final PR will focus on applying operations sent from the server to the editor.