[Feat/add description to record]

[ekgns33]

작업 내역

• 기록 상세조회 시 응답 필드 추가

Summary by CodeRabbit

• New Features
  • Added a description field to the record detail view, allowing users to see record descriptions.
• Bug Fixes
  • Improved consistency in how image URLs are set for record details.
• Tests
  • Enhanced tests to verify that updates to a record’s title, description, and image URL are correctly reflected after editing.

[pull-request-size]

Hi there 👋

Using this App for a private organization repository requires a paid subscription.

You can click Edit your plan on the Pull Request Size GitHub Marketplace listing to upgrade.

If you are a non-profit organization or otherwise can not pay for such a plan, contact me by creating an issue

[coderabbitai]

Walkthrough

A new description field was added to the RecordDetailViewResponse record, with updates to its static factory method to populate this field. The test for updating user records was enhanced to verify that the updated description, title, and image URL are correctly reflected after an update via a subsequent GET request.

Changes

File(s)	Change Summary
src/main/java/org/runimo/runimo/records/service/usecases/dtos/RecordDetailViewResponse.java	Added a description field to the response DTO; updated the static factory method to set this field; refactored builder usage for consistency.
src/test/java/org/runimo/runimo/records/api/RecordAcceptanceTest.java	Enhanced the update test to verify the updated record's fields (title, description, image URL) via a GET request.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant API
    participant Service
    participant DB

    User->>API: PATCH /records/{id} (update record)
    API->>Service: updateRecord(id, payload)
    Service->>DB: Update record in database
    DB-->>Service: Success
    Service-->>API: Updated record response
    API-->>User: 200 OK

    User->>API: GET /records/{id}
    API->>Service: getRecord(id)
    Service->>DB: Fetch record by id
    DB-->>Service: Record entity
    Service-->>API: RecordDetailViewResponse (with description)
    API-->>User: 200 OK + record data

Loading

Poem

In fields of code where records grow,
A new description now will show.
With tests that check each patch and get,
The details bloom—no need to fret!
🐇✨
Each update now is crystal clear,
The rabbit hops and gives a cheer!

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b08e6de and 60d0d2c.

📒 Files selected for processing (2)

• src/main/java/org/runimo/runimo/records/service/usecases/dtos/RecordDetailViewResponse.java (2 hunks)
• src/test/java/org/runimo/runimo/records/api/RecordAcceptanceTest.java (1 hunks)

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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? Join our Discord community 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 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.

[jeeheaG]

Gooood ~