Skip to content
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

Fix: Resource filters in mobile view #10402

Open
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

Rishith25
Copy link
Contributor

@Rishith25 Rishith25 commented Feb 5, 2025

Proposed Changes

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

  • Add specs that demonstrate bug / test a new feature.
  • Update product documentation.
  • Ensure that UI text is kept in I18n files.
  • Prep screenshot or demo video for changelog entry, and attach it to issue.
  • Request for Peer Reviews
  • Completion of QA

Summary by CodeRabbit

  • New Features

    • Enhanced the layout and responsiveness of the ResourceList component for improved user experience on all device sizes.
  • Style

    • Updated the styling of the EmptyState paragraph for better visibility.
    • Improved the layout of resource type and status tabs for a more flexible display.
    • Made the Separator component visible on all screen sizes.
    • Adjusted the status tabs for better content expansion and overflow handling.

@Rishith25 Rishith25 requested a review from a team as a code owner February 5, 2025 01:52
Copy link
Contributor

coderabbitai bot commented Feb 5, 2025

Walkthrough

The update modifies the ResourceList component to enhance its layout and visibility, particularly for responsive design. Changes include making previously hidden elements visible on all screen sizes, ensuring that resource type and status tabs are consistently displayed. The Separator component is now always visible, and adjustments have been made to allow better content expansion and display of status options.

Changes

File Path Change Summary
src/components/Resource/ResourceList.tsx Made elements visible on all screen sizes; updated Separator to always be visible; adjusted layout for status tabs with h-auto and overflow-hidden; enhanced TabsList for better responsiveness.

Assessment against linked issues

Objective Addressed Explanation
Filter buttons not visible in mobile view (#10381)

Possibly related PRs

Suggested labels

needs review, tested

Suggested reviewers

  • shivankacker

Poem

Hop, hop, hop! I'm a little rabbit,
Skipping through code in a happy habit.
Tabs now flex, and styles are bright,
Filtering resources feels just right.
With every change, our UI sings,
A joyful dance as new code springs!
🐰✨


📜 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 c816ee9 and 38177bf.

📒 Files selected for processing (1)
  • src/components/Resource/ResourceList.tsx (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/components/Resource/ResourceList.tsx
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Redirect rules - care-ohc
  • GitHub Check: Header rules - care-ohc
  • GitHub Check: Pages changed - care-ohc
  • GitHub Check: cypress-run (1)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • 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.

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. (Beta)
  • @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

netlify bot commented Feb 5, 2025

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit 38177bf
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/67aa06a8c673240008d9da4e
😎 Deploy Preview https://deploy-preview-10402--care-ohc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@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: 0

🧹 Nitpick comments (3)
src/components/Resource/ResourceList.tsx (3)

201-273: Add aria-labels to improve accessibility

The Select components should include aria-labels for better screen reader support.

Apply these changes to improve accessibility:

-                  <Select
+                  <Select aria-label={t("resource_type_selector")}
                     value={outgoing ? "outgoing" : "incoming"}
                     onValueChange={(value) =>
                       updateQuery({
                         outgoing: value === "outgoing",
                         title,
                       })
                     }
                   >

-                  <Select
+                  <Select aria-label={t("resource_status_group_selector")}
                     value={isActive ? "active" : "completed"}
                     onValueChange={(value) =>
                       updateQuery({
                         status: value === "active" ? "pending" : "completed",
                         title,
                       })
                     }
                   >

-                  <Select
+                  <Select aria-label={t("resource_detailed_status_selector")}
                     value={currentStatus}
                     onValueChange={(value) =>
                       updateQuery({
                         status: value,
                         title,
                       })
                     }
                   >

231-233: Differentiate between status selectors

Two different Select components use the same placeholder "Status" which might be confusing for users.

Consider using more descriptive placeholders:

-                      <SelectValue placeholder={t("Status")} />
+                      <SelectValue placeholder={t("Status Group")} />

-                      <SelectValue placeholder={t("Status")} />
+                      <SelectValue placeholder={t("Detailed Status")} />

Also applies to: 252-254


202-273: Add spacing between mobile selectors

The mobile selectors could benefit from consistent spacing for better visual hierarchy.

Add margin between the selectors:

-                <div className="md:hidden ">
+                <div className="md:hidden space-x-2">
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5d9273d and 75832b7.

📒 Files selected for processing (1)
  • src/components/Resource/ResourceList.tsx (3 hunks)
🔇 Additional comments (2)
src/components/Resource/ResourceList.tsx (2)

24-30: LGTM!

The Select component imports are well-organized and follow the established pattern.


62-62: LGTM!

Good improvement switching to semantic class name text-muted-foreground instead of direct color class.

Copy link
Member

@shivankacker shivankacker left a comment

Choose a reason for hiding this comment

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

I think creating a new component for mobile view will not work out well in the long run and will be redundant. Lets make the existing UI responsive.

@Rishith25
Copy link
Contributor Author

image

@shivankacker Is the above view is fine?

@nihal467
Copy link
Member

nihal467 commented Feb 6, 2025

@shivankacker can you review it

Copy link
Member

@rithviknishad rithviknishad left a comment

Choose a reason for hiding this comment

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

there are invalid classes in this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Filter buttons not visible in mobile view for resource page
5 participants