fix: #2508 Refactor CSS files in src/screens/Leaderboard

[pranavnathe]

What kind of change does this PR introduce?

Refactoring of CSS files related to the Leaderboard screen.

Issue Number:

Fixes #2508

If relevant, did you update the documentation?

No

Summary

This PR refactors the CSS for the Leaderboard screen by moving relevant styles to the global app.module.css file.

Does this PR introduce a breaking change?

No

Other information

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• New Features

  • Introduced a new CSS class for smaller table images, enhancing the display of avatars in the leaderboard.
  • Added a new CSS variable for consistent sizing of small images.

• Bug Fixes

  • Updated styling references to ensure proper rendering of leaderboard components.

[coderabbitai]

Walkthrough

This pull request focuses on refactoring the CSS for the Leaderboard screen by updating the import statement in the Leaderboard.tsx component to use the global app.module.css file. The changes include modifying the import path and adjusting the avatar styling by using a new TableImageSmall CSS class, which sets a smaller image size of 25px. This modification is part of a broader effort to streamline CSS files across the Talawa-Admin application.

Changes

File	Change Summary
src/screens/Leaderboard/Leaderboard.tsx	- Updated CSS import from local to global app.module.css - Changed avatar style from TableImage to TableImageSmall
src/style/app.module.css	- Added new CSS variable --table-image-small-size: 25px - Added new .TableImageSmall class with cover object-fit and fixed size

Assessment against linked issues

Objective	Addressed	Explanation
Streamline CSS into global file [#2508]	✅
Use src/style/app.module.css as single CSS file [#2508]	✅
Delete local CSS files after merging [#2508]	❓	Requires verification of complete CSS file removal

Possibly related issues

• Refactor CSS files in src/screens/CommunityProfile #2503: Refactor CSS files in CommunityProfile screen - Similar CSS consolidation approach.
• Refactor CSS files in src/screens/Requests #2525: Refactor CSS files in Requests screen - Follows the same pattern of CSS streamlining.
• Refactor CSS files in src/screens/EventManagement #2504: Refactor CSS files in EventManagement screen - Consistent with global CSS strategy.

Possibly related PRs

• Chore/organization people UI changes #2358: This PR involves updates to CSS variables and color values, which may indirectly relate to the overall styling changes in the main PR, particularly in how styles are managed across components.
• Refactor styles: move SubTags.module.css styles to app.module.css #2538: This PR consolidates styles into app.module.css, which aligns with the main PR's focus on updating the import paths for styles, indicating a shared goal of streamlining CSS management.
• refactored OrganizationDashboard css/ closes #2513 #2593: Similar to the main PR, this PR refactors CSS files into app.module.css, suggesting a related effort to enhance styling consistency across components.
• refactored: CSS files in src/screens/OrgSettings(fixes: #2523) #2610: This PR also focuses on moving CSS styles to app.module.css, which is directly relevant to the main PR's updates on style imports.
• manage tag css to app.module #2722: This PR's focus on migrating CSS to app.module.css is relevant to the main PR's changes in style imports.
• Refactoring CSS files: merged CommunityProfile styles into global app.module.css #2738: This PR consolidates styles into a global CSS file, which is directly related to the main PR's updates on style management.
• Refactor CSS files in src/screens/OrgList #2764: This PR refactors CSS for the OrgList component, which may relate to the main PR's updates on styling and component structure.
• fixed:#2510 Refactor CSS files in src/screens/ManageTag #2769: This PR also focuses on refactoring CSS files into a global file, aligning with the main PR's objectives.
• [CHORES] Refactor CSS for Org Post  #2774: This PR consolidates styles for the OrgPost component into a global file, which is directly relevant to the main PR's changes in style management.

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

• palisadoes

Poem

🐰 In the realm of styles so grand,
CSS files now march hand in hand
From scattered paths to one true source
A global file sets the right course!
Leaderboard's avatars now shine bright 🌟

---

📜 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 40d386a and d9a593e.

📒 Files selected for processing (1)

• src/style/app.module.css (2 hunks)

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

• src/style/app.module.css

---

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.27%. Comparing base (7755890) to head (d9a593e).
Report is 1 commits behind head on develop-postgres.

Additional details and impacted files

@@                  Coverage Diff                  @@
##           develop-postgres    #2776       +/-   ##
=====================================================
+ Coverage             70.01%   87.27%   +17.25%     
=====================================================
  Files                   296      313       +17     
  Lines                  7358     8204      +846     
  Branches               1606     1848      +242     
=====================================================
+ Hits                   5152     7160     +2008     
+ Misses                 1960      859     -1101     
+ Partials                246      185       -61     

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

[palisadoes]

See comment

[palisadoes]

Thanks. Please fix the conflicting file so we can merge