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

refactored CSS files in src/screens/OrganizationVenues #2879

Open
wants to merge 5 commits into
base: develop-postgres
Choose a base branch
from

Conversation

antriksh-9
Copy link
Contributor

@antriksh-9 antriksh-9 commented Dec 25, 2024

What kind of change does this PR introduce?
refactored CSS files in src/screens/OrganizationVenues

Issue Number:

Fixes #2519

Did you add tests for your changes?
No

Snapshots/Videos:

Screenshot 2024-12-26 031813

If relevant, did you update the documentation?
Not relevant

Summary
The goal is to convert the CSS file in this subdirectory and all the components related to this screen to use this new design pattern.

Does this PR introduce a breaking change?
No

Have you read the contributing guide?
Yes

Summary by CodeRabbit

  • Bug Fixes

    • Removed outdated styles for the organization venues interface, which may affect visual layout.
  • New Features

    • Updated color variables and hover/focus styles to enhance UI components' visual consistency and interactivity.
    • Improved interactivity and visual feedback for dropdown and button components.
    • Introduced new styles for the capacity label and enhanced hover effects for cards.
    • Adjusted styling sources for the VenueCard component to improve visual presentation.

Copy link
Contributor

coderabbitai bot commented Dec 25, 2024

Walkthrough

This pull request focuses on refactoring CSS files for the OrganizationVenues screen by removing the OrganizationVenues.module.css file and updating the global app.module.css with new styles and hover effects. The changes are part of a broader initiative to streamline CSS across the Talawa-Admin application, making it more accessible and maintaining a centralized styling approach.

Changes

File Change Summary
src/screens/OrganizationVenues/OrganizationVenues.module.css Entire CSS file removed
src/style/app.module.css Updated styles including new hover effects, added .capacityLabel class, and modifications to existing dropdown and button styles

Assessment against linked issues

Objective Addressed Explanation
Refactor CSS files in OrganizationVenues [#2519]
Merge CSS into global file [#2519]
Delete subdirectory CSS files [#2519]
Make application more suitable for color-blind users [#2519] Color changes might improve accessibility

Possibly related issues

Possibly related PRs

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

  • palisadoes

Poem

🐰 CSS files hopping away,
Styles merging in a grand display,
Global colors, sharp and bright,
Rabbit's code dance takes flight!
Simplicity wins the day! 🎨


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.

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

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

coderabbitai[bot]
coderabbitai bot previously approved these changes Dec 25, 2024
Copy link
Contributor

@palisadoes palisadoes left a comment

Choose a reason for hiding this comment

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

We spent significant time converting from the predominantly green color scheme to one that is color blind friendly. Please adjust your colors to those that already exist. We are using blue / grey tones in most cases.

src/style/app.module.css Outdated Show resolved Hide resolved
src/style/app.module.css Outdated Show resolved Hide resolved
src/style/app.module.css Outdated Show resolved Hide resolved
src/style/app.module.css Outdated Show resolved Hide resolved
Copy link
Contributor

@palisadoes palisadoes left a comment

Choose a reason for hiding this comment

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

See comments

src/style/app.module.css Outdated Show resolved Hide resolved
src/style/app.module.css Outdated Show resolved Hide resolved
@palisadoes
Copy link
Contributor

Please fix the failing tests

coderabbitai[bot]
coderabbitai bot previously approved these changes Dec 26, 2024
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/style/app.module.css (2)

53-63: Set base opacity for pseudo-elements.

The hover effects look good, but consider setting the base opacity for the pseudo-elements (::before and ::after) to ensure consistent behavior across browsers.

+.cards::before,
+.cards::after {
+  opacity: 0;
+}
.cards:hover {
  filter: brightness(0.8);
}
.cards:hover::before {
  opacity: 0.5;
}
.cards:hover::after {
  opacity: 1;
  mix-blend-mode: normal;
}

74-88: Use CSS variables and avoid !important.

Consider these improvements:

  1. Use a CSS variable for the background color instead of hardcoding.
  2. Remove the !important flag by increasing selector specificity if needed.
+:root {
+  --capacity-label-bg: #31bb6b;
+}
.capacityLabel {
-  background-color: #31bb6b !important;
+  background-color: var(--capacity-label-bg);
  color: white;
  height: 22.19px;
  font-size: 12px;
  font-weight: bolder;
  padding: 0.1rem 0.3rem;
  border-radius: 0.5rem;
  position: relative;
  overflow: hidden;
}
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9c399d7 and 514035b.

📒 Files selected for processing (2)
  • src/components/Venues/VenueCard.tsx (1 hunks)
  • src/style/app.module.css (3 hunks)
✅ Files skipped from review due to trivial changes (1)
  • src/components/Venues/VenueCard.tsx
🔇 Additional comments (4)
src/style/app.module.css (4)

65-72: LGTM! Grid layout is well implemented.

The grid layout handling for odd/even cards is correctly implemented using appropriate selectors.


227-229: LGTM! Good accessibility enhancement.

The focus outline improves keyboard navigation accessibility and follows best practices by using CSS variables with fallbacks.


237-240: LGTM! Well-structured dropdown item interactions.

The hover and focus states are well implemented with appropriate visual feedback using consistent CSS variables.

Also applies to: 245-248


377-384: LGTM! Good interactive feedback.

The hover and active states provide clear visual feedback with appropriate use of color changes and transform effects.

coderabbitai[bot]
coderabbitai bot previously approved these changes Dec 26, 2024
Copy link

codecov bot commented Dec 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.60%. Comparing base (471f113) to head (0a33429).
Report is 50 commits behind head on develop-postgres.

Additional details and impacted files
@@                  Coverage Diff                  @@
##           develop-postgres    #2879       +/-   ##
=====================================================
+ Coverage             63.58%   88.60%   +25.02%     
=====================================================
  Files                   296      316       +20     
  Lines                  7371     8278      +907     
  Branches               1610     1813      +203     
=====================================================
+ Hits                   4687     7335     +2648     
+ Misses                 2451      721     -1730     
+ Partials                233      222       -11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@antriksh-9
Copy link
Contributor Author

@palisadoes
fixed failed tests.

Copy link
Contributor

@palisadoes palisadoes left a comment

Choose a reason for hiding this comment

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

see comment

src/style/app.module.css Outdated Show resolved Hide resolved
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: 1

♻️ Duplicate comments (1)
src/style/app.module.css (1)

377-384: 🛠️ Refactor suggestion

Use CSS variables for color consistency.

The hover state uses a hard-coded color value which should be replaced with a CSS variable to maintain design consistency.

Apply this diff to improve color consistency:

 .searchButton:hover {
-  background-color: var(--search-button-hover-bg, #286fe0);
+  background-color: var(--bs-primary);
   border-color: var(--search-button-border);
 }
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 514035b and 18a8f41.

📒 Files selected for processing (1)
  • src/style/app.module.css (3 hunks)
🔇 Additional comments (2)
src/style/app.module.css (2)

53-72: LGTM: Well-implemented hover effects and grid layout.

The hover effects using filter and opacity provide smooth visual feedback, while the grid layout adjustments ensure consistent presentation for odd/even card counts.


227-229: LGTM: Good accessibility implementation.

The focus and hover states provide clear visual indicators using consistent styling through CSS variables, which improves accessibility.

Also applies to: 237-240

src/style/app.module.css Outdated Show resolved Hide resolved
@palisadoes
Copy link
Contributor

Please make CodeRabbit.ai approve your changes

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/style/app.module.css (2)

53-63: Consider performance implications of filter effects.

The hover effects using filter and mix-blend-mode might impact performance on low-end devices. Consider using simpler CSS properties like opacity or background-color for better performance.

 .cards:hover {
-  filter: brightness(0.8);
+  background-color: rgba(0, 0, 0, 0.2);
 }

74-88: Add RTL support for icon margins.

The implementation looks good overall, but consider using logical properties for better RTL support.

 .capacityLabel svg {
-  margin-bottom: 3px;
+  margin-block-end: 3px;
 }
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 18a8f41 and 0a33429.

📒 Files selected for processing (1)
  • src/style/app.module.css (3 hunks)
🔇 Additional comments (3)
src/style/app.module.css (3)

65-72: LGTM! Grid layout implementation is well-structured.

The grid layout adjustments for odd/even number of cards are implemented correctly and provide good responsive behavior.


227-229: LGTM! Good accessibility enhancement.

The focus styles improve keyboard navigation accessibility and maintain consistency with the design system through CSS variables.


377-384: Maintain consistent color scheme.

Based on previous feedback, color changes should align with the existing design system.

 .searchButton:hover {
-  background-color: var(--search-button-hover-bg, #286fe0);
+  background-color: var(--search-button-hover-bg, #a8c7fa);
   border-color: var(--search-button-border);
 }

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.

2 participants