fixed:#2510 Refactor CSS files in src/screens/ManageTag

[gurramkarthiknetha]

What kind of change does this PR introduce?

Refactoring

Issue Number:

Fixes #2510

Did you add tests for your changes?

No (Not applicable for this refactoring task).

Snapshots/Videos:

Not applicable.

If relevant, did you update the documentation?

Not applicable for this task.

Summary

This PR focuses on refactoring the CSS files in src/screens/ManageTag and its related components to align with the unified design system in Talawa-Admin.

Key objectives achieved:

1. Consolidated all CSS styles into a single global file (src/style/app.module.css).
2. Improved UI/UX for color-blind users by adhering to accessibility standards.
3. Deleted all redundant CSS files in src/screens/ManageTag and its related components.
4. Updated all references in the affected components to use the global CSS file.

This refactoring improves maintainability and consistency across the application.

Does this PR introduce a breaking change?

No

Other information

The foundational work for this refactoring was completed in PR: Chore/css changes #2466. This work builds on that effort to finalize the migration to the unified CSS design.

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• Bug Fixes

  • Removed outdated styles affecting the tag management interface.

• Chores

  • Cleaned up unused CSS to enhance application performance and maintainability.

[coderabbitai]

Caution

Review failed

The head commit changed during the review from 7d4bb02 to dee6b25.

Walkthrough

The pull request involves the removal of the ManageTag.module.css file from the src/screens/ManageTag directory. This change is part of a broader initiative to streamline CSS files across the Talawa-Admin application by consolidating styles into a single global CSS file (src/style/app.module.css). The removal of this specific CSS module is in line with the project's goal of improving UI/UX and making the application more accessible.

Changes

File	Change Summary
src/screens/ManageTag/ManageTag.module.css	Entire CSS file removed as part of CSS refactoring effort

Assessment against linked issues

Objective	Addressed	Explanation
Merge CSS into global file [#2510]	✅
Delete local CSS files [#2510]	✅
Reference global CSS file [#2510]	❓	Dependent on component implementation

Possibly related issues

• Refactor CSS files in src/screens/SubTags #2526: Similar CSS refactoring for SubTags screen
• Refactor CSS files in src/screens/OrganizationTags #2518: Similar CSS refactoring for OrganizationTags screen
• Refactor CSS files in src/screens/EventManagement #2504: Similar CSS refactoring for EventManagement screen

Possibly related PRs

• manage tag css to app.module #2722: Direct relation to CSS migration for ManageTag styles

Suggested reviewers

• palisadoes

Poem

🐰 CSS files hopping away,
Merging styles in a global display,
Streamlined code, clean and bright,
Talawa-Admin's UI taking flight!
Rabbit's refactor, a coding delight! 🌈

---

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.08%. Comparing base (86d59c2) to head (dee6b25).

Additional details and impacted files

@@                  Coverage Diff                  @@
##           develop-postgres    #2737       +/-   ##
=====================================================
+ Coverage             75.56%   87.08%   +11.52%     
=====================================================
  Files                   295      312       +17     
  Lines                  7289     8148      +859     
  Branches               1593     1840      +247     
=====================================================
+ Hits                   5508     7096     +1588     
+ Misses                 1518      875      -643     
+ Partials                263      177       -86     

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

[palisadoes]

Closing. There are no files in this PR