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

Add hover state to ResourceRequests state badges #10035

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

Conversation

rajku-dev
Copy link
Contributor

@rajku-dev rajku-dev commented Jan 18, 2025

Proposed Changes

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

  • Style
    • Enhanced status badge hover effects with color changes for different states (Pending, Approved, Rejected, Completed)
    • Improved visual feedback when hovering over status badges

@rajku-dev rajku-dev requested a review from a team as a code owner January 18, 2025 01:44
Copy link
Contributor

coderabbitai bot commented Jan 18, 2025

Walkthrough

The pull request modifies the ResourceRequests component in the Patient Details Tab, specifically updating the getStatusBadge function. The changes focus on enhancing the visual interaction of status badges by adding hover effects to different status types (PENDING, APPROVED, REJECTED, COMPLETED) and the default badge. These modifications improve the user interface by providing visual feedback when users hover over status badges, making the interactive elements more intuitive.

Changes

File Change Summary
src/components/Patient/PatientDetailsTab/ResourceRequests.tsx Added hover styles to status badges for PENDING, APPROVED, REJECTED, COMPLETED, and default states

Assessment against linked issues

Objective Addressed Explanation
Fix Button Hover Color Issue [#10033]

Possibly related PRs

Suggested reviewers

  • rithviknishad

Poem

🐰 Hover badges dance with glee,
Colors shifting, wild and free!
From gray to green, from red to blue,
Interactive elements shine through!
A rabbit's UI design delight! 🎨


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 Jan 18, 2025

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit f229cf6
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/678b077b2fa143000895b62f
😎 Deploy Preview https://deploy-preview-10035--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.

@rajku-dev rajku-dev changed the title Issue/9888/hover black Add hover state to ResourceRequests state badges Jan 18, 2025
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 (1)
src/components/Patient/PatientDetailsTab/ResourceRequests.tsx (1)

53-58: Consider optimizing badge styles for reusability.

The badge implementation is solid with proper fallback handling, but could benefit from some improvements:

  1. Extract status badge styles to a shared constant or theme file for reuse across components:
// src/theme/badges.ts
export const STATUS_BADGE_STYLES = {
  PENDING: `bg-yellow-100 text-yellow-800 hover:bg-yellow-200 hover:text-yellow-900`,
  // ... other statuses
  default: `bg-gray-100 text-gray-800 hover:bg-gray-200 hover:text-gray-900`
} as const;
  1. Optimize className assignment:
-      <Badge
-        className={
-          statusColors[status] ||
-          "bg-gray-100 text-gray-800 hover:bg-gray-200 hover:text-gray-900"
-        }
-      >
+      <Badge className={statusColors[status] ?? STATUS_BADGE_STYLES.default}>
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c5c52b6 and f229cf6.

📒 Files selected for processing (1)
  • src/components/Patient/PatientDetailsTab/ResourceRequests.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: cypress-run (1)
  • GitHub Check: OSSAR-Scan
🔇 Additional comments (2)
src/components/Patient/PatientDetailsTab/ResourceRequests.tsx (2)

43-58: Overall implementation looks good! 👍

The hover effects are consistently implemented across all status types, maintaining a good balance between visual feedback and semantic meaning. The implementation is type-safe and includes proper fallback handling.


43-49: Verify color contrast ratios for accessibility.

While the hover effects are consistently implemented, please ensure the color combinations meet WCAG contrast requirements for accessibility.

Run the following to find similar color patterns that might need the same accessibility verification:

Consider using template literals for better readability:

 const statusColors: Record<ResourceRequest["status"], string> = {
-      PENDING:
-        "bg-yellow-100 text-yellow-800 hover:bg-yellow-200 hover:text-yellow-900",
+      PENDING: `
+        bg-yellow-100 text-yellow-800
+        hover:bg-yellow-200 hover:text-yellow-900
+      `,
✅ Verification successful

Color combinations are part of a validated design system

The search results show these color combinations are consistently used across multiple components in the application, following Tailwind's accessible color palette patterns. The hover state transitions (background 100->200, text 800->900) are standardized throughout the codebase, suggesting these combinations have been validated for accessibility.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for Tailwind color classes to identify other UI elements that might need accessibility verification
rg "bg-(?:yellow|green|red|blue)-(?:100|200).*?text-(?:yellow|green|red|blue)-(?:800|900)" --type ts --type tsx

Length of output: 141


Script:

#!/bin/bash
# Search for similar color patterns in TypeScript and React files
# Using simpler patterns and explicit file extensions

# Search for background color patterns
echo "=== Background Color Patterns ==="
rg "bg-(yellow|green|red|blue)-(100|200)" --type-add 'tsx:*.tsx' --type-add 'ts:*.ts' -t tsx -t ts

# Search for text color patterns
echo -e "\n=== Text Color Patterns ==="
rg "text-(yellow|green|red|blue)-(800|900)" --type-add 'tsx:*.tsx' --type-add 'ts:*.ts' -t tsx -t ts

Length of output: 8932

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.

Fix Button Hover Color Issue on Requests Table Status Field
1 participant