manage tag css to app.module

[MayankJha014]

Migrate CSS to Global Styles from src/screens/ManageTag

ManageTag css imported to app.module.css

Issue #2510

Summary by CodeRabbit

• Bug Fixes

  • Removed outdated styles for the Manage Tag screen, improving overall UI consistency.

• New Features

  • Introduced a new class for scrollable divs to enhance tag management layout.

• Improvements

  • Updated existing styles for better responsiveness and user interaction, including hover and focus states for breadcrumb navigation and links.
  • Enhanced button container layout for improved visual consistency across the application.
  • Improved control over row display with updated overflow properties.

[coderabbitai]

Walkthrough

The pull request involves refactoring CSS files for the Manage Tag screen by consolidating styles from ManageTag.module.css into the global app.module.css file. This change is part of a broader effort to streamline CSS across the Talawa Admin application, improving UI/UX and making the styling more consistent. The modifications include updating existing classes, adding new styles, and removing module-specific CSS files.

Changes

File	Change Summary
src/screens/ManageTag/ManageTag.module.css	Deleted file, styles merged into app.module.css
src/style/app.module.css	- Added .manageTagScrollableDiv class - Updated .rowBackground with max-height - Enhanced .tagsBreadCrumbs and .subTagsLink with hover/focus styles - Modified .btnsContainer and .btnsBlock layout properties

Possibly related issues

• Refactor CSS files in src/screens/ManageTag #2510: Directly addresses the goal of refactoring CSS files in src/screens/ManageTag and consolidating styles into a global CSS file.
• Refactor CSS files in src/screens/SubTags #2526: Part of the broader initiative to streamline CSS across different screens.
• Refactor CSS files in src/screens/OrganizationTags #2518: Consistent with the project-wide effort to centralize CSS styling.

Possibly related PRs

• Refactor styles: move SubTags.module.css styles to app.module.css #2538: Shares similar approach of moving module-specific styles to app.module.css.
• refactored: CSS files in src/screens/OrgSettings(fixes: #2523) #2610: Consolidates CSS files into app.module.css.
• Refactoring CSS files: merged PageNotFound styles into global app.module.css #2698: Merges styles into global CSS file, following the same pattern.

Suggested reviewers

• AVtheking
• palisadoes
• pranshugupta54

Poem

🐰 Hop, hop, CSS on the move!
Styles dancing to a unified groove
Module files, now just a memory
Global CSS, our new styling spree
Rabbit's refactor, clean and 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 bb90c6d and 9b5a22c.

📒 Files selected for processing (1)

• src/style/app.module.css (4 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

[coderabbitai]

Actionable comments posted: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 139e985 and bb90c6d.

📒 Files selected for processing (2)

• src/screens/ManageTag/ManageTag.module.css (0 hunks)
• src/style/app.module.css (4 hunks)

💤 Files with no reviewable changes (1)

• src/screens/ManageTag/ManageTag.module.css

🔇 Additional comments (2)

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

441-447: LGTM! Well-structured scrollable div class.

The new .manageTagScrollableDiv class follows good practices:

• Uses CSS variables consistently
• Maintains consistency with other scrollable div classes
• Implements proper scrollbar styling

---

449-453: LGTM! Enhanced user interaction with hover styles.

The hover styles for .tagsBreadCrumbs improve accessibility by providing clear visual feedback on interaction.

[palisadoes]

1. Ensure that CodeRabbit.ai approves your work

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.35%. Comparing base (139e985) to head (9b5a22c).
Report is 1 commits behind head on develop-postgres.

Additional details and impacted files

@@                 Coverage Diff                  @@
##           develop-postgres    #2722      +/-   ##
====================================================
+ Coverage             79.58%   86.35%   +6.76%     
====================================================
  Files                   295      312      +17     
  Lines                  7274     8134     +860     
  Branches               1592     1841     +249     
====================================================
+ Hits                   5789     7024    +1235     
+ Misses                 1222      933     -289     
+ Partials                263      177      -86     

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

[MayankJha014]

1. Ensure that CodeRabbit.ai approves your work

Working on it

[MayankJha014]

1. Ensure that CodeRabbit.ai approves your work

Sir @palisadoes code raddit ai approved it and can you please assign me and then merge it