Skip to content

Conversation

JCQuintas
Copy link
Member

I've noticed we use ChartsWrapper in some demos, though that was meant as an internal component. Eg: https://mui.com/x/react-charts/pie/#composition

Due to recent changes to it, it might be better if we properly export it so users can have the same functionality in their composition as our default charts, if they want it ofc

@JCQuintas JCQuintas self-assigned this Jul 29, 2025
@JCQuintas JCQuintas requested a review from alexfauquette as a code owner July 29, 2025 16:23
@JCQuintas JCQuintas added the type: bug It doesn't behave as expected. label Jul 29, 2025
@JCQuintas JCQuintas added plan: Pro Impact at least one Pro user. scope: charts Changes related to the charts. labels Jul 29, 2025
@mui-bot
Copy link

mui-bot commented Jul 29, 2025

Deploy preview: https://deploy-preview-18966--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/DataGrid 0B(0.00%) 0B(0.00%)
@mui/x-data-grid-pro 0B(0.00%) 0B(0.00%)
@mui/x-data-grid-pro/DataGridPro 0B(0.00%) 0B(0.00%)
@mui/x-data-grid-premium 0B(0.00%) 0B(0.00%)
@mui/x-data-grid-premium/DataGridPremium 0B(0.00%) 0B(0.00%)
@mui/x-charts 🔺+21B(+0.01%) 🔺+7B(+0.01%)
@mui/x-charts-pro 🔺+97B(+0.02%) 🔺+34B(+0.03%)
@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 5321daa

Copy link

codspeed-hq bot commented Jul 29, 2025

CodSpeed Performance Report

Merging #18966 will not alter performance

Comparing JCQuintas:export-wrapper (5321daa) with master (b6a7156)1

Summary

✅ 10 untouched benchmarks

Footnotes

  1. No successful run was found on master (55e1427) during the generation of this report, so b6a7156 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

Copy link
Member

@bernardobelchior bernardobelchior left a comment

Choose a reason for hiding this comment

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

Good catch 💯

Comment on lines 1 to 14
import {
ChartsWrapper as OriginalChartsWrapper,
ChartsWrapperProps as OriginalChartsWrapperProps,
} from '../ChartsWrapper';
/**
* @deprecated Use `ChartsWrapper` from `@mui/x-charts/ChartsWrapper` instead.
* This will be removed in the next major version.
*/
export const ChartsWrapper = OriginalChartsWrapper;
/**
* @deprecated Use `ChartsWrapperProps` from `@mui/x-charts/ChartsWrapper` instead.
* This will be removed in the next major version.
*/
export type ChartsWrapperProps = OriginalChartsWrapperProps;
Copy link
Member

Choose a reason for hiding this comment

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

This is the internals directory. Do we need to re-export the file? I was under the impression that content under internals isn't guaranteed not to change within majors.

Still, if we want to keep it, it's probably better to add a task here.

@JCQuintas JCQuintas changed the title [charts-pro] Export ChartsWrapper from package [charts-pro] Export ChartsWrapper from './ChartsWrapper' rather than './internals' Jul 30, 2025
@JCQuintas JCQuintas enabled auto-merge (squash) July 30, 2025 08:55
@JCQuintas JCQuintas merged commit 1ca592e into mui:master Jul 30, 2025
21 checks passed
@JCQuintas JCQuintas deleted the export-wrapper branch July 30, 2025 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plan: Pro Impact at least one Pro user. scope: charts Changes related to the charts. type: bug It doesn't behave as expected.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants