Repository navigation
[Refactor] public 모듈 레이어 구조 정리 - #83
Conversation
- presentation/application/domain/infrastructure 기준으로 파일 재배치
|
Warning Review limit reached
More reviews will be available in 20 minutes and 48 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (97)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
📌 개요
presentation,application,domain,infrastructure레이어 구조로 재배치했습니다.✨ 작업 내용
presentation계층으로 정리했습니다.application계층으로 정리했습니다.domain/entities, 리포지토리는infrastructure계층으로 분리했습니다.presentation계층으로 이동했습니다.api/public/common/presentation으로 이동했습니다.DatabaseModule의 entity glob을 새 레이어 구조에서도 TypeORM 엔티티를 찾을 수 있도록 보정했습니다.🔥 변경 이유
🧪 테스트
pnpm lint:check통과pnpm test통과pnpm build통과🔗 관련 이슈