feat: Refactor useAgentChat hook for better maintainability #148
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
added 8 commits
June 15, 2025 14:53
- Split 1058-line useAgentChat into 7 focused hooks: - useMessages: Message state management and persistence (105 lines) - useRequestControl: AbortController and request lifecycle (53 lines) - useChatUIState: UI state management (loading, reasoning, tools) (40 lines) - useSessionManager: Session management and title generation (131 lines) - useToolExecution: Tool execution and guardrail logic (205 lines) - useStreamChat: Streaming communication and content processing (457 lines) - useAgentChatRefactored: Main hook integrating all components (311 lines) Benefits: - Single Responsibility Principle: Each hook has one clear purpose - Improved testability: Smaller, focused units can be tested independently - Better reusability: Individual hooks can be used in different contexts - Enhanced maintainability: Easier to understand and modify specific functionality - Reduced complexity: No single file exceeds 500 lines Total lines: 1058 → 1391 (includes type definitions and exports) Net complexity reduction through better organization and separation of concerns.
- Fix import syntax error in useAgentChatRefactored.ts - Apply automatic formatting with prettier to all refactored files - Resolve all ESLint warnings related to code formatting
- Fix incorrect import paths in index.ts - Replace AttachedImage import with local type definition - Fix variable naming conflicts (messages -> messagesHook) - Add explicit return statement for TypeScript compliance - Make checkAndGenerateTitle async to match expected signature - Resolve type mismatches in function parameters
- Add missing closing brace for useCallback function body - Fix syntax error that was preventing compilation
- Fix persistMessage function calls to include sessionId parameter - Update generateTitleForCurrentSession signature to accept messages parameter - Wrap persistMessage calls with proper async/await and null checks - Fix return type inconsistencies across hooks
- Add sessionId parameter to persistMessage in useStreamChat - Update useToolExecution to accept 3-parameter streamChat function - Add AbortSignal parameter to streamChat calls in useToolExecution - Fix persistMessage wrapper in useAgentChatRefactored to handle optional sessionId
- Add sessionId parameter to addUserMessage function signature - Resolve remaining TypeScript errors in useAgentChatRefactored calls
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.
Refactor useAgentChat Hook into Modular Components
概要
1058行の巨大な
useAgentChatフックを7つの専門化されたフックに分割してリファクタリングしました。問題
解決策
分割された新しいフック構造
1. useMessages (105行)
2. useRequestControl (53行)
3. useChatUIState (40行)
4. useSessionManager (131行)
5. useToolExecution (205行)
6. useStreamChat (457行)
7. useAgentChatRefactored (311行)
メリット
✅ 単一責任の原則: 各フックが明確な責任を持つ
✅ テスト性の向上: 小さな単位でのテストが可能
✅ 再利用性の向上: 個別フックの他コンテキストでの利用
✅ 保守性の向上: 特定機能の理解・修正が容易
✅ 複雑性の削減: 500行を超えるファイルがない
統計
使用方法
今後の作業
リファクタリングにより、コードの保守性と理解しやすさが大幅に向上しました。