fix(GuageChart): modify the color, font size, and scale text of the dashboard text

[wenbin-eng]

Summary by CodeRabbit

• Visual Improvements
  • Updated gauge chart styling with new color and text size configurations
  • Enhanced axis label and detail text appearance
  • Refined color scheme for chart components

[coderabbitai]

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.

src/components/GaugeChart/handleSeries.js

Oops! Something went wrong! :(

ESLint: 8.56.0

ReferenceError: require is not defined in ES module scope, you can use import instead
This file is being treated as an ES module because it has a '.js' file extension and '/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.
at file:///eslint.config.js?mtime=1737009985614:1:15
at ModuleJob.run (node:internal/modules/esm/module_job:262:25)
at async onImport.tracePromise.proto (node:internal/modules/esm/loader:483:26)
at async loadFlatConfigFile (/node_modules/.pnpm/[email protected]/node_modules/eslint/lib/eslint/flat-eslint.js:299:21)
at async calculateConfigArray (/node_modules/.pnpm/[email protected]/node_modules/eslint/lib/eslint/flat-eslint.js:378:28)
at async FlatESLint.lintFiles (/node_modules/.pnpm/[email protected]/node_modules/eslint/lib/eslint/flat-eslint.js:741:25)
at async Object.execute (/node_modules/.pnpm/[email protected]/node_modules/eslint/lib/cli.js:421:23)
at async main (/node_modules/.pnpm/[email protected]/node_modules/eslint/bin/eslint.js:152:22)

Walkthrough

The pull request introduces visual styling modifications for the gauge chart component. The changes focus on updating color properties and font sizes for axis labels and detail text. Specifically, the modifications involve replacing color tokens and adjusting text rendering in both the handleSeries.js and GaugeChart.js files, with an emphasis on introducing a new colorTextSecondary property to enhance the chart's visual presentation.

Changes

File	Change Summary
src/components/GaugeChart/handleSeries.js	- Updated axis label color from chartToken.axisLabelColor to chartToken.descRichColor - Modified detail text name color and increased font size from 14 to 20
src/feature/token/factory/chartsToken/GaugeChart.js	- Added colorTextSecondary to destructured aliasToken - Integrated colorTextSecondary into descRichColor property

Possibly related PRs

• feat(CircleProcessChart): add markLine #114: Changes to CircleProcessChart/handleSeries.js involving chart series representation
• fix(CircleProcessChart): rectify width exceptions #117: Modifications to chart font size and styling in CircleProcessChart configuration

Poem

🥕 A Rabbit's Chart Delight 🥕

Colors dancing, tokens bright,
Gauge chart styling takes its flight,
Secondary hues now shine so clear,
Font size grows without a fear,
A visual feast for coding's might! 🐰📊

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a4e45a5 and f7011dc.

📒 Files selected for processing (2)

• src/components/GaugeChart/handleSeries.js (3 hunks)
• src/feature/token/factory/chartsToken/GaugeChart.js (1 hunks)

🔇 Additional comments (4)

src/feature/token/factory/chartsToken/GaugeChart.js (1)

13-13: LGTM! Token configuration changes look good.

The addition of colorTextSecondary and its usage as descRichColor aligns well with the PR's objective of modifying dashboard text colors.

Also applies to: 21-21

src/components/GaugeChart/handleSeries.js (3)

132-132: LGTM! Consistent color token usage.

The axis label color now uses the new descRichColor token, maintaining consistency with the design system.

---

473-473: LGTM! Consistent default color configuration.

The default axis label color configuration maintains consistency by using the same descRichColor token.

---

150-151: Verify the impact of increased font size.

The font size increase from 14 to 20 for the name text is significant. Please ensure this doesn't cause any layout issues or text overlapping in different viewport sizes and with various text lengths.

✅ Verification successful

Font size change is properly handled and safe

The increased font size of 20 is safe to use because:

• It's consistently used across multiple chart types in the codebase
• The gauge chart has adequate spacing with 24px top padding
• The chart uses relative positioning (center: 50%) and sizing (radius: 50%) which ensures proper scaling across viewports

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any existing font size definitions or layout constraints for gauge chart name text
rg -A 2 "fontSize.*20" 
rg -A 2 "name.*padding"

Length of output: 3522

---

Script:

#!/bin/bash
# Search for gauge chart size constraints and text handling
rg -A 3 "gauge.*width|gauge.*height" 
ast-grep --pattern 'overflow: $_'
rg -A 2 "truncate.*gauge|ellipsis.*gauge"

Length of output: 118

---

Script:

#!/bin/bash
# Search for gauge chart configuration and container settings
rg -A 5 "type.*gauge" 
rg -A 5 "GaugeChart.*series"
rg -A 3 "chart.*container|chart.*wrapper"

Length of output: 48136

Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.

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.