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

refactor: apply button variants for consistent styling #10589

Closed

Conversation

areebahmeddd
Copy link
Contributor

@areebahmeddd areebahmeddd commented Feb 13, 2025

Proposed Changes

Implementing changes based on the comments in the closed PR (#10574)

Screenshot of the changes: (Clear indication of the "Remove" button)

{37C5F036-9C47-495B-858C-511E9B818903}

@ohcnetwork/care-fe-code-reviewers

Summary by CodeRabbit

  • Style
    • Enhanced the visual design of removal buttons, providing a clear and consistent destructive appearance for delete actions across the application.

Copy link
Contributor

coderabbitai bot commented Feb 13, 2025

Walkthrough

This pull request modifies two components by changing the variant property of the Button component used for removing organizations and questionnaires from "ghost" to "destructive". This change enhances the visual distinction of these buttons as critical actions. Additionally, the Trash2 icon's class has been updated to remove the "text-destructive" class, affecting its color styling. No alterations to the underlying logic or control flow were made.

Changes

File(s) Change Summary
src/components/Patient/LinkDepartmentsSheet.tsx
src/components/Questionnaire/QuestionnaireForm.tsx
Changed Button component's variant from "ghost" to "destructive" for remove actions, and updated the Trash2 icon's class.

Possibly related PRs

Suggested labels

tested, reviewed

Suggested reviewers

  • rithviknishad
  • Jacobjeevan

Poem

In the code garden I happily hop,
Bringing style to buttons with a purposeful pop.
With variants so bold, destructive yet neat,
I paint the UI, a visual treat.
A rabbit's joy in every tiny tweak!
🥕🐇


📜 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 9603693 and 484b91c.

📒 Files selected for processing (2)
  • src/components/Patient/LinkDepartmentsSheet.tsx (1 hunks)
  • src/components/Questionnaire/QuestionnaireForm.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • src/components/Patient/LinkDepartmentsSheet.tsx
  • src/components/Questionnaire/QuestionnaireForm.tsx
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: cypress-run (1)
  • GitHub Check: OSSAR-Scan

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 13, 2025

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit 484b91c
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/67adb7a6df196f00088abd36
😎 Deploy Preview https://deploy-preview-10589.preview.ohc.network
📱 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.

@areebahmeddd areebahmeddd marked this pull request as ready for review February 13, 2025 09:05
@areebahmeddd areebahmeddd requested a review from a team as a code owner February 13, 2025 09:05
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: 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 6c5cefc and 9603693.

📒 Files selected for processing (2)
  • src/components/Patient/LinkDepartmentsSheet.tsx (2 hunks)
  • src/components/Questionnaire/QuestionnaireForm.tsx (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: cypress-run (1)

@@ -4,7 +4,7 @@ import { Building, Loader2, Trash2 } from "lucide-react";
import { useState } from "react";
import { toast } from "sonner";

import { Button } from "@/components/ui/button";
import { Button, buttonVariants } from "@/components/ui/button";
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix incorrect usage of buttonVariants.

The current implementation has several issues:

  1. buttonVariants is meant for button elements, not icons
  2. Applying it to the icon within a button that already has a variant creates conflicting styles

Apply this diff to fix the styling:

-<Button
-  variant="ghost"
-  size="icon"
-  onClick={() => removeOrganization(org.id)}
-  disabled={isRemoving}
->
-  {isRemoving ? (
-    <Loader2 className="h-4 w-4 animate-spin" />
-  ) : (
-    <Trash2
-      className={buttonVariants({ variant: "destructive" })}
-    />
-  )}
-</Button>
+<Button
+  variant="destructive"
+  size="icon"
+  onClick={() => removeOrganization(org.id)}
+  disabled={isRemoving}
+>
+  {isRemoving ? (
+    <Loader2 className="h-4 w-4 animate-spin" />
+  ) : (
+    <Trash2 className="h-4 w-4" />
+  )}
+</Button>

Also applies to: 227-229

@@ -9,7 +9,7 @@ import { cn } from "@/lib/utils";
import CareIcon from "@/CAREUI/icons/CareIcon";

import { Alert, AlertDescription, AlertTitle } from "@/components/ui/alert";
import { Button } from "@/components/ui/button";
import { Button, buttonVariants } from "@/components/ui/button";
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix conflicting button variants.

The button has conflicting style variants:

  1. variant="ghost" prop
  2. buttonVariants({ variant: "destructive" }) in className

Apply this diff to fix the styling:

 <Button
   type="button"
-  variant="ghost"
+  variant="destructive"
   size="sm"
   onClick={() => {
     setQuestionnaireForms((prev) =>
       prev.filter(
         (f) => f.questionnaire.id !== form.questionnaire.id,
       ),
     );
   }}
   disabled={isPending}
-  className={buttonVariants({ variant: "destructive" })}
 >
   <CareIcon icon="l-times-circle" />
   <span>Remove</span>
 </Button>

Also applies to: 392-409

@rithviknishad
Copy link
Member

This was purposefully kept not destructive as this button is not the primary focus on these pages.

This feels there is extra emphasis on the page.

@areebahmeddd areebahmeddd deleted the feat/button-refactor branch February 14, 2025 05:56
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.

Delete button lacks distinct styling in confirmation modal
2 participants