Fix: #1073 refont quests stats

[adrianvrj]

Pull Request type

Please add the labels corresponding to the type of changes your PR introduces:

• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)

Resolves: #1073

Other information

Current output:

Summary by CodeRabbit

• Style

  • Removed gradient text effect from statistics values for a simpler appearance.

• Refactor

  • Updated the statistics component structure by replacing the outer wrapper and adjusting text color handling.

[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 2, 2025 6:15pm

[coderabbitai]

Walkthrough

The changes update the StatElement UI component by replacing its outer wrapper and removing the transparent color from the value text. Corresponding CSS for gradient text styling is eliminated, resulting in a simplified, non-gradient display for stat values. No changes are made to the component's logic or exported entities.

Changes

File(s)	Change Summary
components/UI/stats/statElement.tsx	Changed outer wrapper from Box to div; removed color="transparent" from value Typography.
styles/components/stats.module.css	Removed gradient text styling from .statValue class, eliminating background and text fill rules.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant StatElement
    User->>StatElement: Render StatElement
    StatElement->>StatElement: Render <div> wrapper
    StatElement->>StatElement: Display value without gradient or transparent color

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Refactor the data cards to match the Figma design (#1073)	✅
Remove gradient text and transparent color from stat value as per new design (#1073)	✅
Update UI wrapper structure for stat elements as specified in Figma (#1073)	✅

Possibly related PRs

• color of Quest Analytics changed #1184: Both PRs remove the color="transparent" property from a Typography component and eliminate gradient text styling, indicating related changes to text color and styling in UI components.

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/[email protected]
npm error Found: [email protected]
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/[email protected]
npm error node_modules/@eslint-community/eslint-utils
npm error @eslint-community/eslint-utils@"^4.2.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/utils
npm error @typescript-eslint/utils@"5.62.0" from @typescript-eslint/[email protected]
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 [email protected]
npm error 5 more (@typescript-eslint/type-utils, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^6.0.0 || ^7.0.0 || ^8.0.0" from @typescript-eslint/[email protected]
npm 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 [email protected]
npm error node_modules/eslint-config-next
npm error dev eslint-config-next@"^14.0.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error peer eslint@"^6.0.0 || ^7.0.0 || ^8.0.0" from @typescript-eslint/[email protected]
npm 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 [email protected]
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-02T18_15_47_089Z-eresolve-report.txt
npm error A complete log of this run can be found in: /.npm/_logs/2025-07-02T18_15_47_089Z-debug-0.log

✨ Finishing Touches

• 📝 Generate Docstrings

---

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 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.

[vercel]

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

A member of the Team first needs to authorize it.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

components/UI/stats/statElement.tsx (1)

3-3: Remove unused Box import.

Since the Box component is no longer used in this file, the import should be removed to keep the code clean.

-import Box from "../box";

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 020e1d1 and dac5ec3.

📒 Files selected for processing (2)

• components/UI/stats/statElement.tsx (1 hunks)
• styles/components/stats.module.css (0 hunks)

💤 Files with no reviewable changes (1)

• styles/components/stats.module.css

🧰 Additional context used

🧠 Learnings (1)

components/UI/stats/statElement.tsx (1)

Learnt from: baitcode
PR: lfglabs-dev/starknet.quest#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.

🔇 Additional comments (1)

components/UI/stats/statElement.tsx (1)

17-17: LGTM! Color property removal aligns with gradient styling changes.

Removing color="transparent" is correct since the gradient text styling has been eliminated from the CSS. The text will now use the default color instead of relying on CSS gradients for visibility.

[Marchand-Nicolas]

Sorry for the late review, don't hesitate to ping me!

Please fix the responsive on mobile: