kyle/vip-coordinator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refactor copilot.service.ts - split into focused sub-services #14

New Issue
Closed
opened 2026-02-08 06:44:20 -08:00 by kyle · 1 comment
kyle commented 2026-02-08 06:44:20 -08:00
Owner
Copy Link

Context: copilot.service.ts is 2,758 lines - a monolithic service handling scheduling, reporting, utilization, fleet management, and more. This makes it hard to maintain and test.

File: backend/src/copilot/copilot.service.ts

Suggested fix:

  • Split into focused services:
    • CopilotCoreService - message handling, tool dispatch, system prompt
    • CopilotScheduleService - schedule-related tool implementations
    • CopilotReportService - reporting and analytics tools
    • CopilotFleetService - vehicle/driver management tools
  • Keep the main service as a thin orchestrator that delegates to sub-services

Effort: Medium

**Context:** `copilot.service.ts` is 2,758 lines - a monolithic service handling scheduling, reporting, utilization, fleet management, and more. This makes it hard to maintain and test. **File:** `backend/src/copilot/copilot.service.ts` **Suggested fix:** - Split into focused services: - `CopilotCoreService` - message handling, tool dispatch, system prompt - `CopilotScheduleService` - schedule-related tool implementations - `CopilotReportService` - reporting and analytics tools - `CopilotFleetService` - vehicle/driver management tools - Keep the main service as a thin orchestrator that delegates to sub-services **Effort:** Medium
kyle commented 2026-02-08 07:34:35 -08:00
Author
Owner
Copy Link

Split copilot.service.ts (2758 lines) into 5 focused files: copilot.service.ts (orchestrator), copilot-schedule.service.ts, copilot-reports.service.ts, copilot-fleet.service.ts, copilot-vip.service.ts.

Split copilot.service.ts (2758 lines) into 5 focused files: copilot.service.ts (orchestrator), copilot-schedule.service.ts, copilot-reports.service.ts, copilot-fleet.service.ts, copilot-vip.service.ts.
kyle closed this issue 2026-02-08 07:34:35 -08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kyle
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kyle/vip-coordinator#14
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?