Skip to content

fix: consider Text and Link components as rich text #5334

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 23, 2025
Merged

Conversation

TrySound
Copy link
Member

This prevents editing Text and Link components parent and instead enforces editing these components as rich text containers.

This prevents editing Text and Link components parent and instead
enforces editing these components as rich text containers.
@TrySound TrySound requested a review from kof July 23, 2025 15:40
@TrySound TrySound merged commit 94b1fb9 into main Jul 23, 2025
20 of 23 checks passed
@TrySound TrySound deleted the legacy-rich branch July 23, 2025 18:50
TrySound added a commit that referenced this pull request Jul 23, 2025
This prevents editing Text and Link components parent and instead
enforces editing these components as rich text containers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants