[FIX] 이동하지 않은 날에 대한 조건 분기 처리 오류 해결

[young-jin-son]

Issue Number

close #306

As-Is

이동하지 않은 날에도 통계 컴포넌트가 렌더링됐음

To-Be

• 조건 분기 처리 오류 해결

Check List

• 테스트가 전부 통과되었나요?
• 모든 commit이 push 되었나요?
• merge할 branch를 확인했나요?
• Assignee를 지정했나요?
• Label을 지정했나요?

Test Screenshot

(Optional) Additional Description

Summary by CodeRabbit

• Bug Fixes
  • Improved the display logic for feedback and category achievement sections, ensuring they only appear when there is actual feedback data for the day.

[coderabbitai]

Walkthrough

The conditional rendering in DayStatisticsPage was refined to check that dayStatistics.feedbacks exists and contains elements before rendering the feedback and category achievement components, ensuring these components only appear when actual feedback data is present. The fallback message for no movement remains unchanged.

Changes

File(s)	Change Summary
frontend/src/pages/DayStatisticsPage/index.tsx	Refined conditional rendering to verify dayStatistics.feedbacks is defined and non-empty before rendering feedback and category achievement components.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DayStatisticsPage
    participant UI Components

    User->>DayStatisticsPage: Visit Day Statistics Page
    DayStatisticsPage->>DayStatisticsPage: Fetch dayStatistics
    alt feedbacks exist and not empty
        DayStatisticsPage->>UI Components: Render Feedback & Category Achievement
    else no feedbacks
        DayStatisticsPage->>UI Components: Render fallback message (no movement)
    end

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Fix condition so that statistics components do not render on days with no movement (#306)	✅

Assessment against linked issues: Out-of-scope changes

(No out-of-scope changes found.)

Poem

A rabbit hops through lines of code,
Ensuring stats only show when feedback’s bestowed.
No more empty days with empty views,
Only true feedback now shines through.
With every fix, we leap ahead—
Onward, where real data’s spread! 🐇✨

---

📜 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 1bba674 and a6f64a7.

📒 Files selected for processing (1)

• frontend/src/pages/DayStatisticsPage/index.tsx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• frontend/src/pages/DayStatisticsPage/index.tsx

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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