refactor(components): extract useResponseActions hook#60
Merged
Conversation
Move copy / export / cancel / response-change / template-apply / save-as-template / template-modal-save out of DraftTab.tsx into a single hook. Hook owns showTemplateModal + templateModalRating state; shell consumes showTemplateModal as a prop into WorkspaceDialogs. handleClear now calls resetResponseActions() instead of touching those setters individually.
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
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.
What
Seven response-action callbacks move out of `DraftTab.tsx` into `useResponseActions`:
The hook also takes ownership of `showTemplateModal` and `templateModalRating` state.
Shell reduction: 1551 → 1451 LOC (-100 on this PR).
Why
These callbacks cluster around the response text itself — copying it, exporting it, canceling in-flight generation, tracking edits, and saving it as a template. The template modal state belongs with the two template handlers that drive it. Extracting them out of the shell leaves the shell with orchestration-only concerns (handleClear, handleSuggestionApply, conversation-submit, keyboard handlers, tree toggles, view-mode toggles, the imperative handle wire-up, and the JSX tree).
How
Testing
Risk / Notes
Wave 5 status after this PR