Migrate native blocks to somersault#139
Merged
Merged
Conversation
sneridagh
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This PR migrates Aurora-native blocks into the Somersault field so they can flow through the new editor pipeline, while preserving the existing legacy
value-backed path for Plate text blocks.What changed
migrations.server.tsnow migrates any block registered inconfig.blocks.blocksConfigas a Somersault node withtype: "unknown".content-migrations.server.test.tscovers both the legacy value path and the registered native-block path, plus an unregistered block that is left untouched.server.server.tsnow hydrates listing queries from both legacycontent.blocksentries and listings that have already been moved into__somersault__.Why
The server-side migration layer needs to preserve Aurora-native blocks in the Somersault payload instead of dropping them on the floor. That lets the renderer and later editor machinery take over without losing the original block data.
Validation
pnpm --filter @plone/aurora exec vitest --run app/config/server/content-migrations.server.test.ts app/config/server.server.test.ts