Refactored CSS in src/components/EventListCard

[PratapRathi]

What kind of change does this PR introduce?
This PR will Refactor CSS in src/components/EventListCard/EventListCard.tsx.
As mostly CSS already is imported from src/style/app.module.css I deleted the overlapped style prop which is already applied through app.module.css

Issue Number:
Fixes #2905

Did you add tests for your changes?
N/A

Snapshots/Videos:

If relevant, did you update the documentation?
N/A

Summary
Does this PR introduce a breaking change?
No
Other information
N/A

Have you read the contributing guide?
Yes

Summary by CodeRabbit

• Style
  • Removed inline background color styling for event card
  • Updated component export method

[coderabbitai]

Walkthrough

The pull request involves modifications to the EventListCard.tsx component, focusing on CSS refactoring and export statement adjustment. The changes align with the ongoing effort to streamline CSS across the Talawa-Admin application by removing inline styles and consolidating the component's export declaration.

Changes

File	Change Summary
src/components/EventListCard/EventListCard.tsx	- Removed inline background color style - Updated export statement from separate line to default export

Assessment against linked issues

Objective	Addressed	Explanation
Remove embedded CSS [#2905]	✅
Merge CSS into global file [#2905]	❓	No explicit evidence of merging into app.module.css

Possibly related issues

• Refactor CSS files in src/screens/EventManagement #2504: Similar CSS refactoring effort in Event Management screens
• Refactor CSS files in src/screens/OrganizationEvents #2514: CSS refactoring in Organization Events
• Refactor CSS in src/screens/UserPortal/Events/Events.tsx #2892: CSS refactoring in User Portal Events

Suggested reviewers

• varshith257
• palisadoes

Poem

🐰 A rabbit's tale of code so neat,
Styles removed, export made sweet
CSS dancing to a global tune
Refactoring done, success hewn!
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 c8a1290 and 71a7302.

📒 Files selected for processing (1)

• src/components/EventListCard/EventListCard.tsx (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• src/components/EventListCard/EventListCard.tsx

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

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

---

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

[rishav-jha-mech]

LGTM
There is no requirement of adding styles to app.module.css as the styles which are being used currently in this file is already present there.

[PratapRathi]

LGTM There is no requirement of adding styles to app.module.css as the styles which are being used currently in this file is already present there.

Yes @rishav-jha-mech the style is already present in app.module.css and relevant class is applied to the component already, that's why I removed the style attribute.