Skip to content

Conversation

@mapache-salvaje
Copy link
Contributor

@mapache-salvaje mapache-salvaje commented Oct 2, 2025

No description provided.

@mapache-salvaje mapache-salvaje added docs Improvements or additions to the documentation. type: enhancement It’s an improvement, but we can’t make up our mind whether it's a bug fix or a new feature. scope: charts Changes related to the charts. labels Oct 2, 2025
@mui-bot
Copy link

mui-bot commented Oct 2, 2025

Deploy preview: https://deploy-preview-19793--material-ui-x.netlify.app/

Updated pages:

Bundle size report

Bundle Parsed size Gzip size
@mui/x-data-grid 0B(0.00%) 0B(0.00%)
@mui/x-data-grid-pro 0B(0.00%) 0B(0.00%)
@mui/x-data-grid-premium 0B(0.00%) 0B(0.00%)
@mui/x-charts 0B(0.00%) 0B(0.00%)
@mui/x-charts-pro 0B(0.00%) 0B(0.00%)
@mui/x-charts-premium 0B(0.00%) 0B(0.00%)
@mui/x-date-pickers 0B(0.00%) 0B(0.00%)
@mui/x-date-pickers-pro 0B(0.00%) 0B(0.00%)
@mui/x-tree-view 0B(0.00%) 0B(0.00%)
@mui/x-tree-view-pro 0B(0.00%) 0B(0.00%)

Details of bundle changes

Generated by 🚫 dangerJS against 9c74f51

@codspeed-hq
Copy link

codspeed-hq bot commented Oct 2, 2025

CodSpeed Performance Report

Merging #19793 will not alter performance

Comparing mapache-salvaje:feature/dx-45-revise-the-charts-custom-components-doc (4c8a5d3) with master (75b09d6)

Summary

✅ 13 untouched

Copy link
Member

@alexfauquette alexfauquette left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took advantage of this PR to spot few sentences we forgot to updat efrom one major to another 🫣

@mapache-salvaje mapache-salvaje marked this pull request as ready for review October 20, 2025 14:37

- `height` and `width` for the `<svg />` size. If not provided, those values are derived from the container.
- `margin` for adding space between the `<svg />` border and the **drawing area**.
- `height` and `width` for the SVG size; if not provided, these values are derived from the container
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe easier by avoiding details

Suggested change
- `height` and `width` for the SVG size; if not provided, these values are derived from the container
- `height` and `width` for the SVG size


Series information is accessible through the `useSeries` hook for all series types, and `useXxxSeries` hook for a specific series type.
These hooks return the order of the series and their configuration, including data points, color, among others.
Series information is accessible through the `useSeries()` hook for all series types, and the `useXxxSeries()` hook for a specific series type.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mui/xcharts I believe we started using use*Series from the discussion here: #19334 (comment)

Suggested change
Series information is accessible through the `useSeries()` hook for all series types, and the `useXxxSeries()` hook for a specific series type.
Series information is accessible through the `useSeries()` hook for all series types, and the `use*Series()` hook for a specific series type.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I missed this comment. For me use*Series() is not intuitive. It looks more like a typo than a place to fill with other values.

image

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The page below adds context to what this is though, in that use-case at least 🤔
In the current use case we might want to add like useBarSeries for example

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's maybe cultural, but for me stars are for stuff like sx, f**k, sht, ...

I would prefer one of those options.

  • use***Series() to specify "there are multiple characters missing"
  • useXxxSeries() to specify "there are a caml case word"
  • use[Type]Series() to specify the mining of the missing world

Whatever the one we pick, we should modify

To display data, you have components named `<XxxPlot />` such as `<LinePlot />`, `<AreaPlot />`, `<MarkPlot />`, `<BarPlot />`, etc.

## Stabilize `useSeries` and `useXxxSeries` hooks ✅

Series information is accessible through the `useSeries` hook for all series types, and `useXxxSeries` hook for a specific series type.

The `use*Series` hooks provide access to specific series data for a particular chart type.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use[Type]Series() - I think I like this one best because it seems most obvious to me that the text in brackets needs to be replaced. What about use[Chart]Series() instead? In my mind, that makes it immediately clear to me that I can sub in Bar, Line, etc. there.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm also fine with adding a parenthetical on first mention: "...the use[Chart]Series() hook (for example, useBarSeries())..."

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't use[Chart]Series cause confusion? We have a lot of useChart stuff 😆

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair point - let's go with use[Type]Series() then

Co-authored-by: Alexandre Fauquette <[email protected]>
Signed-off-by: mapache-salvaje <[email protected]>
@github-actions
Copy link

This pull request has been inactive for 30 days. Please remove the stale label or leave a comment to keep it open. Otherwise, it will be closed in 15 days.

@github-actions github-actions bot added the stale Inactive for 7 days (issues) or 30 days (PRs); closed after 5 or 15 more days if no update. label Nov 30, 2025
Copy link
Member

@alexfauquette alexfauquette left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JCQuintas Can I let you check the few remaining suggestion I left.

Other than that it looks good to me.

I updated the page to folow the new naming convention Component instead of <Component> or <Component />

@github-actions github-actions bot removed the stale Inactive for 7 days (issues) or 30 days (PRs); closed after 5 or 15 more days if no update. label Dec 1, 2025
@mapache-salvaje
Copy link
Contributor Author

Thanks for reviving this @alexfauquette ! I just did one final pass and I'm happy with it now. 👍

@alexfauquette alexfauquette enabled auto-merge (squash) December 4, 2025 15:35
@alexfauquette alexfauquette merged commit 5405d77 into mui:master Dec 4, 2025
22 checks passed
A-s-h-o-k pushed a commit to A-s-h-o-k/mui-x that referenced this pull request Dec 14, 2025
Signed-off-by: mapache-salvaje <[email protected]>
Co-authored-by: Alexandre Fauquette <[email protected]>
Co-authored-by: alex <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Improvements or additions to the documentation. scope: charts Changes related to the charts. type: enhancement It’s an improvement, but we can’t make up our mind whether it's a bug fix or a new feature.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants