fix(vue): resolve component lifecycle crash in rich text with OL + embedded components #13
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 resolves the component lifecycle crash when editing rich text fields containing ordered lists (OL) and embedded components during live preview (issue #11).
Changes Made
Core Fix
useStoryblokRichTextEnhancedinto the mainuseStoryblokRichTextcomposable for a simpler, unified APIKey Improvements
_uidfor keys to prevent Vue lifecycle issues during re-rendersTest Updates
Code Quality
Technical Details
The original issue occurred when Vue's
resolveComponentwas called outside of a proper render context during live preview updates. The fix ensures components are properly keyed and rendered through the existingStoryblokComponentwrapper, which handles the component resolution safely.Testing
Breaking Changes
None. This maintains full backward compatibility while providing enhanced functionality.
Closes #11