-
Notifications
You must be signed in to change notification settings - Fork 0
chore :: [#112] change dateTime region #123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Walkthrough메시지 저장 시점의 시간대가 시스템 기본값에서 "Asia/Seoul"로 명시적으로 지정되도록 변경되었습니다. 이로 인해 메시지의 Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant SaveMessageUseCase
participant MessageRepository
User->>SaveMessageUseCase: execute(message)
SaveMessageUseCase->>SaveMessageUseCase: get current time (Asia/Seoul)
SaveMessageUseCase->>MessageRepository: save(message, sendTime)
MessageRepository-->>SaveMessageUseCase: confirmation
SaveMessageUseCase-->>User: result
Assessment against linked issues
Poem
✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/main/kotlin/dsm/wemeet/domain/message/usecase/SaveMessageUseCase.kt (1)
33-33: 성능 최적화와 유지보수성 개선을 고려해보세요.타임존 명시가 올바르게 구현되었지만, 다음 개선사항을 제안합니다:
- 성능 최적화:
ZoneId.of("Asia/Seoul")가 매번 호출되어 새 객체를 생성합니다.- 유지보수성: 타임존이 하드코딩되어 있습니다.
클래스 상단에 정적 상수를 추가하는 것을 고려해보세요:
@Service @Transactional class SaveMessageUseCase( + companion object { + private val SEOUL_ZONE_ID = ZoneId.of("Asia/Seoul") + } + private val queryUserService: QueryUserService, // ... ) { // ... - val sendTime = LocalDateTime.now(ZoneId.of("Asia/Seoul")) + val sendTime = LocalDateTime.now(SEOUL_ZONE_ID)또는 설정 파일에서 타임존을 주입받는 방식도 고려할 수 있습니다.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/main/kotlin/dsm/wemeet/domain/message/usecase/SaveMessageUseCase.kt(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Check Code Quality
🔇 Additional comments (1)
src/main/kotlin/dsm/wemeet/domain/message/usecase/SaveMessageUseCase.kt (1)
13-13: Import 추가가 적절합니다.타임존 지정을 위한
ZoneIdimport가 올바르게 추가되었습니다.
|
근데 이거 때문에 잘못된 점이 있나요? 메시지 테이블 확인해보니까 이상할건 없어보였는데 아닌가ㅏ |
|
방금 보낸 데이터도 확인을 해봤는데 |
|
엥 스퀘어 배포 지역이 뭐 어떻게 돼있나 암튼 알겠습니다 ㄱㄱ |
close #122
Summary by CodeRabbit