Skip to content

클래스 Feature의 역할별 Interface 의존성 적용 - #75

Merged
Roy-wonji merged 1 commit into
developfrom
feature/class-feature-interfaces-20261026
Oct 26, 2026
Merged

Roy-wonji merged 1 commit into
developfrom
feature/class-feature-interfaces-20261026

Conversation

@Roy-wonji

Copy link
Copy Markdown
Contributor

변경 내용

  • Class Feature Reducer의 넓은 classUseCase 의존성을 역할별 Interface 키로 교체했습니다.
  • 참여 화면은 Room/Member, 추천 화면은 Recommendation/TopicDraft Interface를 각각 주입합니다.
  • ClassReport 미리보기 주입도 Result Interface에 맞췄습니다.

확인

  • xcodebuild -workspace Picke.xcworkspace -scheme Class -configuration Debug -destination 'generic/platform=iOS Simulator' -derivedDataPath Tuist/.build/class-interface-derived CODE_SIGNING_ALLOWED=NO build -quiet 성공
  • 변경 파일의 git diff --check 통과
  • 테스트는 실행하거나 수정하지 않았습니다. 기존 테스트의 classUseCase 주입 14곳은 후속 확인이 필요합니다.

Class Feature의 단일 classUseCase 참조를 화면 역할에 맞는 Interface 의존성으로 분리합니다. 참여와 추천 화면은 필요한 두 Interface만 주입하고 리포트 미리보기도 결과 Interface에 맞춥니다.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-26T03:38:46.335678Z b57bf9c PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions

Copy link
Copy Markdown
Contributor

제출하신 PR은 Class Feature Reducer의 광범위한 classUseCase 의존성을 역할별(ClassDebateUseCase, ClassBattleUseCase, ClassRoomUseCase, ClassMemberUseCase, ClassResultUseCase, ClassRecommendationUseCase, ClassTopicDraftUseCase, ClassTicketUseCase) 인터페이스 의존성으로 성공적으로 교체했습니다. 이는 모듈 간 결합도를 낮추고 각 컴포넌트의 책임(SRP)을 명확히 하는 좋은 개선점입니다. Effect.run 클로저 내에서 필요한 의존성만 캡처하고, ClassReport 미리보기 주입도 변경된 인터페이스에 맞춰 적절히 수정되었습니다. 전반적으로 프로젝트의 아키텍처와 유지보수성을 향상시키는 긍정적인 변경입니다.

@Roy-wonji
Roy-wonji merged commit 6510aa0 into develop Oct 26, 2026
5 checks passed
@Roy-wonji
Roy-wonji deleted the feature/class-feature-interfaces-20261026 branch October 26, 2026 03:38

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b57bf9c3b5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +157 to +158
@Dependency(\.classRoomUseCase) private var classRoomUseCase
@Dependency(\.classMemberUseCase) private var classMemberUseCase

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Migrate existing overrides to the new dependency keys

The existing test and audit callers still inject classUseCase, which is independent of classRoomUseCase, so these reducers now silently use the default MockClassRepository instead of the supplied stub. For example, ClassDeadlineEditTests.저장_실패는_폼을_남겨_수동_재시도할_수_있다 injects an empty repository to force .invalidCode, but the new key resolves to a populated repository; ClassJoinTests and MyClassTests likewise lose their configured responses and shared repository state. Update the affected test and audit overrides alongside this migration so the existing assertions and coordinator/child state sharing remain valid.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant