fix(tui): ensure forked message text is inserted in prompt (resolves #7257) #7259
+4
−0
Conversation
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
Fixes regression where forking a session via /fork command or message dialog would not insert the selected message text into the prompt input box. The issue was a timing problem where the createEffect that handles route.initialPrompt ran before the prompt ref was assigned during component initialization. Now applies the initial prompt directly in the Prompt component's ref callback, which guarantees the prompt instance is available when setting the initial text. Resolves issue where forked sessions started with empty prompt input boxes.
Contributor
|
The following comment was made by an LLM, it may be inaccurate: No duplicate PRs found |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fixes regression where forking a session via /fork command or message dialog would not insert the selected message text into the prompt input box.
The issue was a timing problem where the createEffect that handles route.initialPrompt ran before the prompt ref was assigned during component initialization.
Now applies the initial prompt directly in the Prompt component's ref callback, which guarantees the prompt instance is available when setting the initial text.
Resolves issue where forked sessions started with empty prompt input boxes.
Resolves #7257.