Swapping boba-editor with boba-editor-next (BEN), for reasons to be documented at some other juncture.
How
We'll do the migration in 2 phases:
cool-phase-name#1: new posts are created (and displayed) through BEN, but boba-editor remains in charge of old posts
cool-phase-name#2: old posts are converted to the new BEN format, and boba-editor is taken out back and shot in a dark alley somewhere given the proper send off and a honorable discharge
cool-phase-name#1
a.k.a. "new posts are created (and displayed) through BEN, but boba-editor remains in charge of old posts"
Notes
Backend changes
This phase doesn't need to touch boba-backend or the DB in any way. boba-components can conditionally display content using either boba-editor OR BEN according to which format the passed JSON is in. This doesn't mean that we can't choose to e.g. tell the db to save old and new content in different columns if we so wish, but just that we're not forced to do backend changes.
Frontend changes
In the ideal case, boba-frontend wouldn't need to be touched either. Any change done there should be reviewed with suspicion and questioned.
Subphases (bugs to be filed)
[ ] An entity in boba-components (e.g. posts, comments) can use BEN to display BEN-format content
[ ] An entity in boba-components (e.g. posts, comments) can conditionally use BEN or boba-editor to display either content
[ ] An editable entity in boba-components (e.g. posts, comments) uses BEN to accept any type of input, with custom restrictions
[ ] An editable entity in boba-components (e.g. posts, comments) can go through the whole upload pipeline (e.g. getting all the included images uploaded) using BEN
[ ] All entities in boba-components are switched to use BEN (a.k.a "rest of the owl")
cool-phase-name#2
a.k.a. old posts are converted to the new BENformat, and boba-editor is taken out back and shot in a dark alley somewhere given the proper send off and a honorable discharge
### Steps
- [ ] Download entire `boba-backend` DB
- [ ] Write a zod query to ensure we know the schema of every post
- [ ] Write a convert function
- [ ] Create a new DB column for the update text
- [ ] Have `boba-backend` server send down both new and old text. Changes to `boba-components` from cool-phase-name#1 should have allowed for displaying either new text if it exists or old text if it does not
- [ ] Slowly convert old posts, monitoring for errors
- [ ] Once all old posts have been converted, delete old text column from the DB
- [ ] Put `boba-editor` out of its misery, and remove no longer needed logic for deciding whether to display new or old text from `boba-components`
Currently blocked on getting BEN to feature parity with boba-editor
Goal
Swapping
boba-editorwithboba-editor-next(BEN), for reasons to be documented at some other juncture.How
We'll do the migration in 2 phases:
BEN, butboba-editorremains in charge of old postsBENformat, andboba-editoristaken out back and shot in a dark alley somewheregiven the proper send off and a honorable dischargecool-phase-name#1
Notes
Backend changes
This phase doesn't need to touch
boba-backendor the DB in any way.boba-componentscan conditionally display content using eitherboba-editorORBENaccording to which format the passed JSON is in. This doesn't mean that we can't choose to e.g. tell the db to save old and new content in different columns if we so wish, but just that we're not forced to do backend changes.Frontend changes
In the ideal case,
boba-frontendwouldn't need to be touched either. Any change done there should be reviewed with suspicion and questioned.Subphases (bugs to be filed)
boba-components(e.g. posts, comments) can useBENto displayBEN-formatcontentboba-components(e.g. posts, comments) can conditionally useBENorboba-editorto display either contentboba-components(e.g. posts, comments) usesBENto accept any type of input, with custom restrictionsboba-components(e.g. posts, comments) can go through the whole upload pipeline (e.g. getting all the included images uploaded) usingBENboba-componentsare switched to useBEN(a.k.a "rest of the owl")cool-phase-name#2