-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[docs] Add a line chart demo for the Overview section #20239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Deploy preview: https://deploy-preview-20239--material-ui-x.netlify.app/ Updated pages: Bundle size report
|
CodSpeed Performance ReportMerging #20239 will not alter performanceComparing Summary
Footnotes |
There's an info here:
|
|
When I had to add a Legend, I had to replace Is there any particular reason why Also, shouldn't |
Yeah, the container is there just to ease it a little bit, but maybe it doesn't provide enough DX improvement and it's a bit confusing.
I guess the benefit is one less component and you don't need to know which props go to the data provider and which ones to the surface. If you look at the implementation, the container is basically only rendering the data provider and the surface.
Yeah, I think we need to make this more homogenous. I'd be more in favor of removing the 's'. If you look at Base UI, the components are named @alexfauquette @JCQuintas what do you think? We could introduce the variant without the 's' now and start migrating. |
IIRC @alexfauquette told me the I can't find the discussion anymore, but I argued that we should move to IIRC this was after the fact that I had created both the
Not sure, doesn't feel super clean. Might as well just do it in one go. |
My point was to ease the migration rather than simplify our life. By supporting both in v8, users can migrate in the last version of v8 minimizing the number of changes they need to do in one go to upgrade to v9. I did the migration from MUI v4 to v5 and it was painful because there were so many changes that it wasn't possible to review or split up PRs. I wouldn't want to cause that now that I'm on this side 😅 |
| const xScale = useXScale(); | ||
| const yScale = useYScale('unemployment-axis'); | ||
| const unemploymentSeries = useLineSeries('unemployment'); | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| const { instance } = useChartContext(); | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not feasible for now since it's an internal hook
| if ( | ||
| x == null || | ||
| y == null || | ||
| x < left || | ||
| x > left + width || | ||
| y < top || | ||
| y > top + height | ||
| ) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| if ( | |
| x == null || | |
| y == null || | |
| x < left || | |
| x > left + width || | |
| y < top || | |
| y > top + height | |
| ) { | |
| if (!instance.isPointInside(x, y)) { |
|
I removed the label for unemployement pick, and simplified the data to only keep months where we have both GDP and unemployement. My idea is: This is a demonstration. We don't need to over complicate the data |
Co-authored-by: alex <alex.fauquette@gmail.com>
Co-authored-by: alex <alex.fauquette@gmail.com>

Source:
https://fred.stlouisfed.org/series/UNRATE
https://fred.stlouisfed.org/series/A939RC0Q052SBEA