Refactor AverageRating component to use CSS modules for styling

[Aayushgoyal00]

What kind of change does this PR introduce?
Refactoring

Issue Number:

Fixes #2902

Did you add tests for your changes?
No

Snapshots/Videos:
https://github.com/user-attachments/assets/5882d06b-dc05-447b-9fc5-709ac1babef8

If relevant, did you update the documentation?
No

Summary

-All embedded CSS in the file (talawa-admin\src\components\EventStats\Statistics\AverageRating.tsx) has been merged into the global CSS file (talawa-admin\src\style\app.module.css) using pre-existing CSS.

-All embedded CSS in this file (talawa-admin\src\components\EventStats\Statistics\AverageRating.tsx) has been removed,

Does this PR introduce a breaking change?
No

Have you read the contributing guide?
Yes

Summary by CodeRabbit

• Style
  • Updated styling for event statistics card and rating components
  • Replaced inline styles with CSS module classes
  • Added custom color variables for rating star states
  • Set consistent card width of 300px

[coderabbitai]

Walkthrough

This pull request focuses on refactoring the CSS styling in the AverageRating.tsx component by transitioning from inline styles to CSS module styling. The changes involve importing styles from app.module.css and replacing inline style definitions with predefined CSS classes. New CSS variables and classes are introduced in the app.module.css file to support the styling of the rating component and card container, aligning with the project's goal of consolidating CSS into a single global file.

Changes

File	Change Summary
src/components/EventStats/Statistics/AverageRating.tsx	- Added import for CSS styles from ../../../style/app.module.css - Replaced inline Card component width style with styles.cardContainer class - Modified Rating component styling from sx prop to classes prop
src/style/app.module.css	- Added CSS variables --rating-star-filled and --rating-star-hover - Added .cardContainer class with 300px width - Added .ratingFilled and .ratingHover classes for rating icon styling

Assessment against linked issues

Objective	Addressed	Explanation
Move embedded CSS to app.module.css	✅
Remove inline CSS references	✅
Improve UI/UX for color-blind users	❓	Color changes made, but full accessibility impact unclear

Possibly related PRs

• Refactor styles: move SubTags.module.css styles to app.module.css #2538: Modifications to app.module.css similar to this PR
• refactored OrganizationDashboard css/ closes #2513 #2593: Consolidation of styles in app.module.css
• Refactor CSS for LeftDrawerOrg #3131: Updates to app.module.css with new styles
• Refactored CSS in src/components/EventListCard #3188: CSS refactoring in another component
• BugFix : Fixed Overflow of images in Advertisement and Venue Post modals #3204: Styling modifications in app.module.css

Suggested reviewers

• palisadoes
• AVtheking

Poem

🐰 CSS dancing, styles so bright,
Modules and classes taking flight,
From inline to global, a stylish delight,
Refactoring magic in CodeRabbit's sight!
Hop, hop, hooray for clean design! 🌈✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3cf1b07 and 74cb9aa.

📒 Files selected for processing (2)

• src/components/EventStats/Statistics/AverageRating.tsx (3 hunks)
• src/style/app.module.css (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• src/components/EventStats/Statistics/AverageRating.tsx
• src/style/app.module.css

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Test Application
• GitHub Check: Analyse Code With CodeQL (javascript)

Finishing Touches

• 📝 Generate Docstrings

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[github-actions]

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]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/style/app.module.css (1)

949-955: Consider using CSS variables for colors.

While the color values work correctly, consider using CSS variables for consistency and maintainability. The file already defines color variables that could be reused.

.ratingFilled {
-  color: #ff6d75;
+  color: var(--red-delete-text);
}

.ratingHover {
-  color: #ff3d47;
+  color: var(--delete-button-color);
}

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 68d6193 and 8370adc.

📒 Files selected for processing (2)

• src/components/EventStats/Statistics/AverageRating.tsx (3 hunks)
• src/style/app.module.css (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyse Code With CodeQL (javascript)

🔇 Additional comments (4)

src/components/EventStats/Statistics/AverageRating.tsx (3)

7-7: LGTM! Import statement for CSS modules added correctly.

The import statement for the CSS module is properly added.

---

36-36: LGTM! Card styling moved to CSS modules.

The inline width style has been correctly replaced with the cardContainer class from CSS modules.

---

53-56: LGTM! Rating component styling moved to CSS modules.

The Rating component's styling has been properly migrated to use CSS module classes for filled and hover states.

src/style/app.module.css (1)

945-947: LGTM! Card container width defined correctly.

The cardContainer class properly sets a fixed width of 300px.

[Cioppolo14]

@Aayushgoyal00 Please fix the failed tests.

[palisadoes]

See comment