Placeholder deletion bug fixed#1056
Merged
ffrose merged 4 commits intoJun 8, 2026
Merged
Conversation
Pull from dev
…into fix/1050/placeholder_deletion_bug
|
Thirunayan22
approved these changes
Jun 8, 2026
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
3 participants
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 pull request simplifies the
handleEditorChangelogic in theTextfieldContentcomponent. The main change is the removal of formatting and template-cleaning logic when handling editor changes, streamlining how the value is processed and passed to the parent.Textfield input handling simplification:
removeNestedTemplatesand direct Quill editor manipulation fromhandleEditorChange, so the raw input value is now passed directly toonChangeand stored in state.