Skip to content

Comments

MOSU-105 refactor: SchoolJpa 도시락 여러 개 추가하도록 변경#106

Merged
jbh010204 merged 1 commit intodevelopfrom
refactor/mosu-105
Jul 16, 2025
Merged

MOSU-105 refactor: SchoolJpa 도시락 여러 개 추가하도록 변경#106
jbh010204 merged 1 commit intodevelopfrom
refactor/mosu-105

Conversation

@jbh010204
Copy link
Member

@jbh010204 jbh010204 commented Jul 16, 2025

✨ 구현한 기능

📢 논의하고 싶은 내용

🎸 기타

Summary by CodeRabbit

  • New Features

    • Added support for managing multiple lunch menu items per school, including lunch name and price.
  • Improvements

    • School registration, editing, and response screens now handle lists of lunch menus instead of single lunch entries.
    • Area details now display a list of available lunch options for each school.
  • Other Changes

    • Updated database schema handling for development environments.

@coderabbitai
Copy link

coderabbitai bot commented Jul 16, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

This change refactors lunch menu handling throughout the school domain and DTOs. It replaces single lunch and price fields with a list of lunch menu objects in entities and request/response DTOs, introduces new classes for lunch menu representation, and updates the database schema generation strategy.

Changes

File(s) Change Summary
.../application/school/SchoolService.java Removed explicit transaction propagation in @Transactional annotation.
.../domain/school/LunchMenu.java Introduced new embeddable LunchMenu class with lunch enum and price fields.
.../domain/school/SchoolJpaEntity.java Replaced single lunch/lunchPrice fields with List<LunchMenu>; updated constructor and methods accordingly.
.../presentation/school/dto/AreaDetail.java Added lunchInfo list field; updated factory method to map lunch menus to LunchInfo list.
.../presentation/school/dto/LunchInfo.java Added new record LunchInfo with lunch name and price fields.
.../presentation/school/dto/LunchMenuRequest.java Added new record LunchMenuRequest with conversion method to domain entity.
.../presentation/school/dto/SchoolEditRequest.java Replaced lunch and price fields with List<LunchMenu>; updated schema annotation.
.../presentation/school/dto/SchoolRegistrationRequest.java Replaced lunch and price fields with List<LunchMenuRequest>; updated entity conversion logic.
.../presentation/school/dto/SchoolResponse.java Replaced lunch and price fields with List<LunchMenu>; updated factory method.
src/main/resources/application.yml Changed Hibernate ddl-auto from update to create-drop.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Controller
    participant DTO
    participant DomainEntity
    participant DB

    Client->>Controller: Submit SchoolRegistrationRequest (with lunchMenus)
    Controller->>DTO: Map request to DTOs (LunchMenuRequest)
    DTO->>DomainEntity: Convert LunchMenuRequest list to LunchMenu list
    DomainEntity->>DB: Persist SchoolJpaEntity with List<LunchMenu>
    DB-->>DomainEntity: Confirmation
    DomainEntity-->>Controller: Persisted entity
    Controller-->>Client: Response with lunchMenus
Loading

Possibly related PRs

Suggested labels

우선순위 중

Suggested reviewers

  • polyglot-k

Poem

In the garden of code, the lunch menus grew,
No longer just one, but a colorful crew!
With lists and with records, the changes took root,
Now every school’s lunch is a multi-choice loot.
Hopping through fields of DTO delight—
This rabbit approves: the future is bright! 🥕


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 351518b and 439f103.

📒 Files selected for processing (10)
  • src/main/java/life/mosu/mosuserver/application/school/SchoolService.java (1 hunks)
  • src/main/java/life/mosu/mosuserver/domain/school/LunchMenu.java (1 hunks)
  • src/main/java/life/mosu/mosuserver/domain/school/SchoolJpaEntity.java (4 hunks)
  • src/main/java/life/mosu/mosuserver/presentation/school/dto/AreaDetail.java (2 hunks)
  • src/main/java/life/mosu/mosuserver/presentation/school/dto/LunchInfo.java (1 hunks)
  • src/main/java/life/mosu/mosuserver/presentation/school/dto/LunchMenuRequest.java (1 hunks)
  • src/main/java/life/mosu/mosuserver/presentation/school/dto/SchoolEditRequest.java (2 hunks)
  • src/main/java/life/mosu/mosuserver/presentation/school/dto/SchoolRegistrationRequest.java (3 hunks)
  • src/main/java/life/mosu/mosuserver/presentation/school/dto/SchoolResponse.java (2 hunks)
  • src/main/resources/application.yml (1 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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 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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @jbh010204, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the SchoolJpaEntity and its associated data transfer objects (DTOs) to enable the storage and management of multiple lunch menus per school, moving away from a single lunch option. This change enhances the flexibility of school data by allowing a more comprehensive representation of available lunch offerings, impacting both the persistence layer and the API's input/output structures.

Highlights

  • Data Model Refactoring: The SchoolJpaEntity has been updated to store a collection of LunchMenu objects, replacing the previous single lunch and lunchPrice fields. This allows a school to offer multiple lunch options.
  • New Embeddable LunchMenu: A new JPA embeddable class LunchMenu was introduced to encapsulate the lunch type and its price, facilitating the storage of multiple lunch options.
  • API DTO Updates: All relevant DTOs (SchoolRegistrationRequest, SchoolEditRequest, SchoolResponse, AreaDetail) have been modified to reflect the new multiple lunch menu structure, including the introduction of LunchMenuRequest (for requests) and LunchInfo (for responses) DTOs.
  • Database Schema Management: The ddl-auto setting in application.yml was changed from update to create-drop, which will recreate the database schema on each application startup. This is typically used for development and testing of schema changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@jbh010204 jbh010204 merged commit 39838cc into develop Jul 16, 2025
1 of 2 checks passed
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request refactors the application to support multiple lunch options for a school. The review focuses on improving the code's robustness and maintainability by addressing a potential NullPointerException, cleaning up the entity constructor, and decoupling the API DTOs from the domain model.

@Schema(description = "도시락 가격")
@NotNull
Integer lunchPrice,
List<LunchMenuRequest> lunchMenus,

Choose a reason for hiding this comment

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

critical

The lunchMenus field can be null if it's omitted from the request payload, causing a NullPointerException in the toEntity() method. Add a @NotNull annotation to enforce that the field is always present in the request.

Suggested change
List<LunchMenuRequest> lunchMenus,
@NotNull
List<LunchMenuRequest> lunchMenus,

Comment on lines 60 to +64
public SchoolJpaEntity(String schoolName, Area area, Lunch lunch, LocalDate examDate,
Long capacity,
LocalDateTime deadlineTime, Integer lunchPrice, AddressJpaVO address) {
LocalDateTime deadlineTime, Integer lunchPrice, AddressJpaVO address,
List<LunchMenu> lunchMenu
) {

Choose a reason for hiding this comment

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

high

The constructor includes an unused parameter lunch. It should be removed to clean up the method signature.

Suggested change
public SchoolJpaEntity(String schoolName, Area area, Lunch lunch, LocalDate examDate,
Long capacity,
LocalDateTime deadlineTime, Integer lunchPrice, AddressJpaVO address) {
LocalDateTime deadlineTime, Integer lunchPrice, AddressJpaVO address,
List<LunchMenu> lunchMenu
) {
public SchoolJpaEntity(String schoolName, Area area, LocalDate examDate,
Long capacity,
LocalDateTime deadlineTime, AddressJpaVO address,
List<LunchMenu> lunchMenu
) {

@NotNull
Integer lunchPrice,
@Schema(description = "점심 메뉴 목록")
List<LunchMenu> lunchMenus,

Choose a reason for hiding this comment

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

high

This request DTO directly uses the domain object LunchMenu. It's better to use dedicated DTOs for API requests to decouple the presentation layer from the domain layer. Use a list of LunchMenuRequest here.

Suggested change
List<LunchMenu> lunchMenus,
List<LunchMenuRequest> lunchMenus,

String area,
String lunch,
Integer lunchPrice,
List<LunchMenu> lunchMenus,

Choose a reason for hiding this comment

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

high

This response DTO exposes the domain object LunchMenu. Use a dedicated DTO for the response, like LunchInfo, for better decoupling.

Suggested change
List<LunchMenu> lunchMenus,
List<LunchInfo> lunchMenus,

school.getArea().getAreaName(),
school.getLunch().getLunchName(),
school.getLunchPrice(),
school.getLunchMenus(),

Choose a reason for hiding this comment

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

high

Map the list of LunchMenu domain objects to a list of LunchInfo DTOs here.

Suggested change
school.getLunchMenus(),
school.getLunchMenus().stream().map(menu -> new LunchInfo(menu.getLunch().getLunchName(), menu.getLunchPrice())).toList(),

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