Make Use Cases grid adaptive based on item count & Unify G6 chart title styles with G2 and improve examples#404
Conversation
|
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…tail pages Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add missing titles to 11 gallery examples (scatter, radar, funnel, venn, violin, flow-diagram, network-graph, organization-chart, indented-tree, mindmap, fishbone-diagram) - Add missing title to waterfall-chart gallery example - Shorten existing long titles (line, bar, column, area, histogram, treemap, boxplot) - Shorten long axis titles (axisYTitle) across line, area, column, dual-axes, violin, bar charts Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Align G6 title font to sans-serif, color to #000 (light) / #e0e6ed (dark) - Add top padding of 46 when G6 chart has a title - Normalize all G6 chart default padding to 20 - Update organization-chart gallery example with simpler text and 3-level data Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
🎊 PR Preview d20f67c has been successfully built and deployed to https://antvis-GPT-Vis-preview-pr-404.surge.sh 🕐 Build time: 0.012s 🤖 By surge-preview |
There was a problem hiding this comment.
Code Review
This pull request refactors the example data for all chart types, introducing a standardized valueType field and simplifying property descriptions. It also updates the chart documentation page with a dynamic grid for use cases and a new Required column in the properties table. Additionally, visualization components were updated to support titles with improved padding and font styling. Review feedback focuses on correcting typos in the boxplot example data and improving font family consistency by using constants or more robust font stacks for chart titles.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

Uh oh!
There was an error while loading. Please reload this page.