Skip to content

[HOTFIX] CustomizeTimeBoxEntity 에서 time 이 nullable 하지 않도록 수정#212

Merged
unifolio0 merged 2 commits intodevelopfrom
hotfix/time-nullable
Aug 1, 2025
Merged

[HOTFIX] CustomizeTimeBoxEntity 에서 time 이 nullable 하지 않도록 수정#212
unifolio0 merged 2 commits intodevelopfrom
hotfix/time-nullable

Conversation

@leegwichan
Copy link
Member

@leegwichan leegwichan commented Aug 1, 2025

🚩 연관 이슈

🗣️ 리뷰 요구사항 (선택)

  • 실시간 리뷰 확인해주세요.

Summary by CodeRabbit

  • 버그 수정
    • 시간 값이 없을 경우 처리 방식이 개선되어, 일부 상황에서 시간 정보가 올바르게 반영됩니다.

@coderabbitai
Copy link

coderabbitai bot commented Aug 1, 2025

Walkthrough

CustomizeTimeBoxEntity 클래스의 생성자 내부에서 time 필드의 초기화 방식이 변경되었습니다. 이제 timeBox.getTime() 값이 null이면 timeBox.getTimePerTeam() * 2로 설정되고, null이 아니면 timeBox.getTime() 값이 그대로 할당됩니다. null 허용 여부에 대한 주석이 추가되었습니다.

Changes

Cohort / File(s) Change Summary
CustomizeTimeBoxEntity 생성자 로직 변경
src/main/java/com/debatetimer/entity/customize/CustomizeTimeBoxEntity.java
생성자에서 time 필드 초기화 로직 변경. timeBox.getTime()이 null이면 timeBox.getTimePerTeam() * 2 할당, 아니면 timeBox.getTime() 할당. null 허용에 대한 주석 추가.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5-10 minutes

Suggested labels

fix


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1a6fa6f and f1fb41a.

📒 Files selected for processing (1)
  • src/main/java/com/debatetimer/entity/customize/CustomizeTimeBoxEntity.java (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/main/java/com/debatetimer/entity/customize/CustomizeTimeBoxEntity.java
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build-and-push
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch hotfix/time-nullable

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@leegwichan leegwichan changed the title []: CustomizeTimeBoxEntity 에서 time 이 nullable 하지 않도록 수정 [HOTFIX] CustomizeTimeBoxEntity 에서 time 이 nullable 하지 않도록 수정 Aug 1, 2025
@leegwichan leegwichan self-assigned this Aug 1, 2025
@leegwichan leegwichan added the hotfix 핫픽스 label Aug 1, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4812031 and 1a6fa6f.

📒 Files selected for processing (1)
  • src/main/java/com/debatetimer/entity/customize/CustomizeTimeBoxEntity.java (1 hunks)
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
Learnt from: coli-geonwoo
PR: debate-timer/debate-timer-be#203
File: src/main/resources/db/migration/V11__add_memberId_into_poll.sql:1-2
Timestamp: 2025-07-24T03:12:25.245Z
Learning: debate-timer 프로젝트에서 poll 관련 테이블들은 아직 운영 환경에 배포되지 않았으므로, NOT NULL 컬럼 추가 시 기존 데이터 백필 전략을 고려할 필요가 없음.
Learnt from: leegwichan
PR: debate-timer/debate-timer-be#198
File: src/test/java/com/debatetimer/domain/customize/CustomizeTimeBoxDomainTest.java:82-112
Timestamp: 2025-07-15T01:28:24.899Z
Learning: CustomizeTimeBoxDomain 클래스에서는 생성자에서 stance null 검증을 먼저 수행한 후 isValidStance() 추상 메서드를 호출하는 구조로 되어 있어, 테스트용 구현체에서 isValidStance()는 단순히 true를 반환해도 된다.
Learnt from: leegwichan
PR: debate-timer/debate-timer-be#198
File: src/test/java/com/debatetimer/domain/customize/CustomizeTimeBoxDomainTest.java:82-112
Timestamp: 2025-07-15T01:28:24.899Z
Learning: CustomizeTimeBoxDomain에서 validateStance 메서드는 null 체크를 먼저 수행한 후에 isValidStance() 추상 메서드를 호출하는 구조로, 테스트용 구현체에서 isValidStance()가 단순히 true를 반환하는 것이 적절하다.
📚 Learning: customizetimeboxdomain 클래스에서는 생성자에서 stance null 검증을 먼저 수행한 후 isvalidstance() 추상 메서드를 호출하는 구조로 되어 있어,...
Learnt from: leegwichan
PR: debate-timer/debate-timer-be#198
File: src/test/java/com/debatetimer/domain/customize/CustomizeTimeBoxDomainTest.java:82-112
Timestamp: 2025-07-15T01:28:24.899Z
Learning: CustomizeTimeBoxDomain 클래스에서는 생성자에서 stance null 검증을 먼저 수행한 후 isValidStance() 추상 메서드를 호출하는 구조로 되어 있어, 테스트용 구현체에서 isValidStance()는 단순히 true를 반환해도 된다.

Applied to files:

  • src/main/java/com/debatetimer/entity/customize/CustomizeTimeBoxEntity.java
📚 Learning: customizetimeboxdomain에서 validatestance 메서드는 null 체크를 먼저 수행한 후에 isvalidstance() 추상 메서드를 호출하는 구조로, 테스...
Learnt from: leegwichan
PR: debate-timer/debate-timer-be#198
File: src/test/java/com/debatetimer/domain/customize/CustomizeTimeBoxDomainTest.java:82-112
Timestamp: 2025-07-15T01:28:24.899Z
Learning: CustomizeTimeBoxDomain에서 validateStance 메서드는 null 체크를 먼저 수행한 후에 isValidStance() 추상 메서드를 호출하는 구조로, 테스트용 구현체에서 isValidStance()가 단순히 true를 반환하는 것이 적절하다.

Applied to files:

  • src/main/java/com/debatetimer/entity/customize/CustomizeTimeBoxEntity.java

@github-actions
Copy link

github-actions bot commented Aug 1, 2025

Test Results

120 files  120 suites   13s ⏱️
272 tests 272 ✅ 0 💤 0 ❌
284 runs  284 ✅ 0 💤 0 ❌

Results for commit f1fb41a.

♻️ This comment has been updated with latest results.

@github-actions
Copy link

github-actions bot commented Aug 1, 2025

📝 Test Coverage Report

Overall Project 87.52% -0.15% 🍏
Files changed 60%

File Coverage
CustomizeTimeBoxEntity.java 89.36% -2.13%

Copy link
Contributor

@unifolio0 unifolio0 left a comment

Choose a reason for hiding this comment

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

LGTM

@unifolio0 unifolio0 merged commit 659991c into develop Aug 1, 2025
5 checks passed
@unifolio0 unifolio0 deleted the hotfix/time-nullable branch August 1, 2025 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotfix 핫픽스

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants