fix(tui): move props.ref to onMount #7702
Merged
+32
−33
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.
Fixes: #7633 & possibly #7634
What does this PR do?
Currently there is an issue where forking from the first message of a session causes a fatal crash since
the session route calls
r.set(route.initialPrompt)immediately after receiving the ref, but theinputis not valid until thetextareacomponent is ready later on-down in the component hierarchy.This PR moves the
Prompt props.reflogic into theonMountlifecycle component to ensure that the ref is only invoked when the component is fully ready.How did you verify your code works?
fork-message-fix.mov