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

Consistent Button Placement and Layout for Users Display Page (#10639) #10643

Conversation

abdulazeespr
Copy link
Contributor

@abdulazeespr abdulazeespr commented Feb 17, 2025

Proposed Changes

image image

@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

  • Style
    • Improved the overall layout of the user card component for a cleaner and more responsive interface.
    • Enhanced element spacing and alignment to ensure content expands appropriately.
    • Adjusted text display to prevent wrapping, keeping usernames concise and readable.
    • Repositioned action buttons for better visual balance.

Sorry, something went wrong.

@abdulazeespr abdulazeespr requested a review from a team as a code owner February 17, 2025 08:30
Copy link
Contributor

coderabbitai bot commented Feb 17, 2025

Walkthrough

This pull request updates the layout and styling of the UserCard component in the UserListAndCard file. The changes involve adding flexbox-related classes directly to components, adjusting the expansion behavior of content containers, enforcing single-line text for usernames with a no-wrap class, and right-aligning a details button. No changes were made to the exported entities.

Changes

File Summary
src/components/Users/UserListAndCard.tsx Added flex flex-col to the Card, updated CardContent with flex flex-col flex-grow, modified the user details container with flex-grow, ensured the username remains on one line with whitespace-nowrap, and restructured the detail button with justify-end.

Suggested labels

needs review, tested

Suggested reviewers

  • Jacobjeevan
  • rithviknishad

Poem

I'm a rabbit hopping through the code,
Flex classes sprouting as I go,
Cards and spans line up so neat,
No-wrap usernames keep the beat,
With button cues and flowing design,
I cheer—hoppy changes shine!


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

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit 3ef6ab7
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/67b2f3c5119f9c000886e725
😎 Deploy Preview https://deploy-preview-10643.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.

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 (2)
src/components/Users/UserListAndCard.tsx (2)

80-81: Consider optimizing nested flex containers.

While the layout works, there are redundant flex properties. The nested flex-col and flex-grow on both parent and child could be simplified.

-      <CardContent className="p-4 sm:p-6 flex flex-col flex-grow">
-        <div className="flex flex-col flex-grow  gap-4">
+      <CardContent className="p-4 sm:p-6 flex flex-col flex-grow gap-4">
+        <div className="h-full">

96-96: Remove redundant whitespace class.

The truncate utility already includes white-space: nowrap. Adding whitespace-nowrap is redundant.

-                  <span className="text-sm text-gray-500 truncate  whitespace-nowrap">
+                  <span className="text-sm text-gray-500 truncate">
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4ecd90a and 3ef6ab7.

📒 Files selected for processing (1)
  • src/components/Users/UserListAndCard.tsx (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: Redirect rules - care-ohc
  • GitHub Check: Header rules - care-ohc
  • GitHub Check: Pages changed - care-ohc
  • GitHub Check: Test
  • GitHub Check: OSSAR-Scan
  • GitHub Check: cypress-run (1)
  • GitHub Check: lint
  • GitHub Check: CodeQL-Build
🔇 Additional comments (2)
src/components/Users/UserListAndCard.tsx (2)

79-79: LGTM! Good use of flexbox for card layout.

The addition of flex flex-col classes to the Card component establishes a proper foundation for consistent vertical layout.


119-121: LGTM! Good button placement and spacing.

The combination of mt-auto, pt-2, and justify-end ensures consistent button placement at the bottom of the card with proper spacing.

Copy link
Contributor

@AdityaJ2305 AdityaJ2305 left a comment

Choose a reason for hiding this comment

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

Hey @abdulazeespr, the department users card is being redesigned in another PR, which is almost ready for merging. Can we apply the same design as you’re now working on the user card?
Screenshot 2025-02-17 at 5 08 14 PM
but , Only proceed if the maintainers confirm it, though 😅
cc: @Jacobjeevan @rithviknishad

Edit: Here is that PR #10568

@@ -116,7 +116,9 @@ const UserCard = ({ user }: { user: UserBase }) => {
</div>
</div>
</div>
<div className="mt-auto pt-2">{GetDetailsButton(user.username)}</div>
<div className="mt-auto pt-2 justify-end">
{GetDetailsButton(user.username)}
Copy link
Member

Choose a reason for hiding this comment

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

although was there previously, let's switch to using proper casings

https://docs.aws.amazon.com/prescriptive-guidance/latest/best-practices-cdk-typescript-iac/typescript-best-practices.html

image
Suggested change
{GetDetailsButton(user.username)}
{getDetailsButton(user.username)}

Copy link
Contributor

Choose a reason for hiding this comment

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

Currently the function uses a hook, #10659 moves it out to the parent component. 🤔 So could copy over the logic or let that PR take care of it.

cc: @rithviknishad

@Jacobjeevan
Copy link
Contributor

Jacobjeevan commented Feb 25, 2025

Closing due to inactivity. Feel free to reopen.

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.

Consistent Button Placement and Layout for Users Display Page
4 participants