依賴注入 - Clean Architecture in TypeScript

 1We are using the `tsyring` to manage our dependencies.
 2
 3Currently, we do not use it to inject dependencies into our classes.
 4
 5Let's update `src/controller` to use `tsyringe` for dependency injection.
 6
 7> The `src/controller` is our entrypoint will initialize the usecase.
 8
 9```typescript
10const repository = container.resolve(CartRepositoryToken);
11// ...
12const query = new GetCartQuery(repository);
13```
14
15The usecase do not depend on the 3rd-party library, so we cannot set it as `injectable`, therefore we manually resolve it in the controller.
16
17For other components, e.g. repository, service, presenter, we can use `@injectable()` decorator to mark them as injectable.
18
19- `src/container.ts` is the file where we register our dependencies.
20- `src/usecase/interface.ts` is the file where we define our interfaces and tokens for dependency injection.
21
22Let's refactor the `src/controller` to use `tsyringe` for dependency injection. 

 1Plan: Refactor Controllers to Use tsyringe Dependency InjectionStep 1: Create Container Configuration (src/container.ts)
 2
 3- Define dependency injection tokens for all interfaces
 4- Register concrete implementations for repositories, presenters, and services
 5- Configure the tsyringe container with proper bindings
 6
 7Step 2: Add Injectable Decorators
 8
 9- Add @injectable() to all repository classes (KvCartRepository, KvChatMessageRepository, MockProductRepository)
10- Add @injectable() to all presenter classes (JsonCartPresenter, JsonChatMessagePresenter, etc.
11- Add @injectable() to service classes (LlmAssistantService) - with special handling for constructor dependencies
12
13Step 3: Update Interface Tokens (src/usecase/interface.ts
14
15- Add injection tokens for each interface (e.g., CartRepositoryToken, ChatMessageRepositoryToken
16- Export tokens for use in controllers
17
18Step 4: Refactor Cart Controller (src/controller/cart.ts)
19
20- Replace manual instantiation with container.resolve()
21- Use tokens to resolve dependencies
22- Maintain existing API structure and functionality
23
24Step 5: Refactor Chat Controller (src/controller/chat.ts)
25
26- Replace manual instantiation with container.resolve()
27- Handle complex dependencies (LlmAssistantService with env parameter)
28- Use tokens for all repository and presenter dependencies
29
30Step 6: Handle Special Cases
31
32- Configure LlmAssistantService to handle Cloudflare env injection
33- Ensure proper lifecycle management for request-scoped dependencies
34
35This refactoring will:
36- Centralize dependency management
37- Improve testability through dependency injection
38- Follow Clean Architecture principles
39- Maintain existing API contracts
40- Make the codebase more maintainable