feat: add hover styles to cards

[luighis]

📐 Features

✅ Added styles when hovering over cards
✅ The animations and colors are consistent with the other cards, improving the user experience.

closes #1168

Grabacion.de.pantalla.2025-07-26.a.la.s.1.01.41.a.m.mov

Summary by CodeRabbit

• Style
  • Enhanced the hover effect on opportunity cards with smoother transitions, a subtle lift, updated background color, and a gentle shadow for improved visual feedback.

[vercel]

@luighis is attempting to deploy a commit to the LFG Labs Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
starknet-quest	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 26, 2025 4:15am

[coderabbitai]

Walkthrough

The update modifies the CSS classes applied to the root div of the DefiOpportunityCardComponent. The new classes introduce a more elaborate hover effect, including vertical translation, a custom background color, and a shadow, using smooth transitions. No changes were made to the component's structure or functionality.

Changes

File(s)	Change Summary
components/discover/defiOpportunityCard.tsx	Updated root div CSS classes to implement a unified, smoother hover animation with translation, background color, and shadow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

❌ Change request

Suggested reviewers

• Marchand-Nicolas

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/eslint-plugin@5.62.0
npm error Found: eslint@9.30.0
npm error node_modules/eslint
npm error dev eslint@"^9.11.1" from the root project
npm error peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.7.0
npm error node_modules/@eslint-community/eslint-utils
npm error @eslint-community/eslint-utils@"^4.2.0" from @typescript-eslint/utils@5.62.0
npm error node_modules/@typescript-eslint/utils
npm error @typescript-eslint/utils@"5.62.0" from @typescript-eslint/eslint-plugin@5.62.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error dev @typescript-eslint/eslint-plugin@"^5.47.0" from the root project
npm error 1 more (eslint-config-next)
npm error 1 more (@typescript-eslint/type-utils)
npm error @eslint-community/eslint-utils@"^4.2.0" from eslint@9.30.0
npm error 5 more (@typescript-e

... [truncated 730 characters] ...

error node_modules/@typescript-eslint/eslint-plugin
npm error dev @typescript-eslint/eslint-plugin@"^5.47.0" from the root project
npm error @typescript-eslint/eslint-plugin@"^5.4.2 || ^6.0.0 || ^7.0.0 || ^8.0.0" from eslint-config-next@14.2.30
npm error node_modules/eslint-config-next
npm error dev eslint-config-next@"^14.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /.npm/_logs/2025-07-26T04_14_47_064Z-eresolve-report.txt
npm error A complete log of this run can be found in: /.npm/_logs/2025-07-26T04_14_47_064Z-debug-0.log

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[luighis]

Hi @Marchand-Nicolas , check the PR, please.
Any questions, let me know, I'll be happy to answer you.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 437b350 and c5bcfc0.

📒 Files selected for processing (1)

• components/discover/defiOpportunityCard.tsx (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: fricoben
PR: lfglabs-dev/starknet.quest#963
File: components/discover/defiTable.tsx:418-456
Timestamp: 2024-11-25T01:01:20.940Z
Learning: When displaying opportunity cards in the `DataTable` component (`components/discover/defiTable.tsx`), ensure that data is rendered dynamically based on the current filters and sorting applied, avoiding hardcoded values.

Learnt from: baitcode
PR: lfglabs-dev/starknet.quest#962
File: app/page.tsx:34-34
Timestamp: 2024-11-27T07:42:52.459Z
Learning: In this project, updating the Card component to use Next.js Image component is considered out of scope.

components/discover/defiOpportunityCard.tsx (5)

Learnt from: fricoben
PR: #963
File: components/discover/defiTable.tsx:418-456
Timestamp: 2024-11-25T01:01:20.940Z
Learning: When displaying opportunity cards in the DataTable component (components/discover/defiTable.tsx), ensure that data is rendered dynamically based on the current filters and sorting applied, avoiding hardcoded values.

Learnt from: baitcode
PR: #962
File: app/page.tsx:34-34
Timestamp: 2024-11-27T07:42:52.459Z
Learning: In this project, updating the Card component to use Next.js Image component is considered out of scope.

Learnt from: baitcode
PR: #962
File: components/pages/home/splitTitle.tsx:373-392
Timestamp: 2024-11-27T07:25:07.612Z
Learning: In the SplitTitle component (components/pages/home/splitTitle.tsx), the use of Math.random() in the getVariants function is intentional to create unpredictable animations.

Learnt from: joeperpetua
PR: #870
File: components/discover/tokenIcon.tsx:19-29
Timestamp: 2024-10-11T11:08:32.705Z
Learning: In the TokenIcon component (components/discover/tokenIcon.tsx), when an unknown token is encountered, default to using the USDC icon, consistent with the implementation in TokenSymbol (components/quest-boost/TokenSymbol.tsx).

Learnt from: baitcode
PR: #962
File: components/pages/home/splitTitle.tsx:3-3
Timestamp: 2024-11-27T07:26:15.265Z
Learning: In the file components/pages/home/splitTitle.tsx, the motion library is correctly imported from motion/react rather than framer-motion.

[Marchand-Nicolas]

Perfect, great job, lgtm! :D