Version Packages - #3184
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Bundle Stats✅ No significant changes. All scenario measurements (7)🗺️
Significant means at least 1.0 KB and 1% gzip, or at least 5 ms and 10% import time. |
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@portabletext/editor@8.0.3
Patch Changes
#3182
ec6191eThanks @christianhg! - fix: locate a renamed node by its new key when undoing a_keychangeUndoing an edit that renamed a node's own
_key(a collision-avoiding rename ahead of a block merge, for example) left the node stuck under its new key instead of restoring the old one: the undo step tried to find the node by the key it had before the rename, which no longer resolved to anything once the rename had applied. Undoing now locates the node by its current key first, so a rename reverts cleanly along with everything else in the same undo step.#3182
f910394Thanks @christianhg! - fix: re-point positions only at the renamed node's own path when a_keychangesRenaming a node's
_keyno longer drags carets, selections, or tracked ranges sitting on an unrelated node that happens to carry the same key (keys are only unique among siblings, so twins across blocks are legal). Positions on the renamed node itself follow the rename as before; everything else stays put.#3182
e653db5Thanks @christianhg! - fix: rename colliding keys before a text block merge deletes the merging blockMerging a text block into its neighbor (backspace at its start, or forward delete at the end of the block before it) could silently mint fresh
_keys for any child span or annotation whose key collided with one already in the destination block. On the wire this read as those nodes being destroyed and re-created rather than moved, so a collaborator applying the same patches lost their caret through the merge instead of following it. The merge now renames the colliding keys first, so the emitted patches express the rename followed by the move instead of a destroy-and-create.@portabletext/plugin-character-pair-decorator@9.0.3
Patch Changes
@portabletext/plugin-emoji-picker@8.0.3
Patch Changes
@portabletext/plugin-markdown-shortcuts@9.0.3
Patch Changes
@portabletext/plugin-typeahead-picker@7.0.3
Patch Changes
@portabletext/plugin-typography@9.0.3
Patch Changes
@portabletext/plugin-dnd@2.0.3
@portabletext/plugin-input-rule@7.0.3
@portabletext/plugin-list-index@2.0.3
@portabletext/plugin-one-line@8.0.3
@portabletext/plugin-paste-link@5.0.3
@portabletext/plugin-sdk-value@8.0.3
@portabletext/plugin-table@2.0.3
@portabletext/toolbar@9.0.3