[docs] Chart example with responsive container and tooltip demo is broken

[karolis-666]

Related page

https://mui.com/x/react-charts/tooltip/#tooltip-position

Kind of issue

Broken demo

Issue description

Opening example in code editor displays missing files

Context

No response

Search keywords: chart, charts, responsive, tooltip

Search keywords:

[alexfauquette]

@karolis-666 I assume it's only broken in codesandbox because it's working when I load the page

The cause is the nested import. The files imported from the demo should not have import themself

[karolis-666]

It's the only example I found that has responsive container and shows tooltip implementation for them.

Exploring source code I can't find those files which are required, so I can't simply understand logic how to implement given example in my code

[k-rajat19]

@karolis-666 you can see them here https://github.com/mui/mui-x/tree/master/docs/data/charts/tooltip for now
@alexfauquette can we pass those as a prop in CustomTooltipPosition or is there any more appropriate fix for that ?

[alexfauquette]

It's the only example I found that has a responsive container and shows tooltip implementation for them.

On my computer, I can see them in the docs. Is there something specific to your browser? Could you try in private navigation without extensions?

Capture.video.du.2024-10-23.17-24-35.mp4

@k-rajat19 Yes that would be an option. Another one would be to to copy-past then them in each file. Or restart the effort on mui/material-ui#44150

[karolis-666]

These two files imported in code example are not present

Open this code in codesandbox or stackblitz and you'll see they are missing - app crashing

[alexfauquette]

Thanks for clarification. Then we will restart the effort on mui/material-ui#44150 and if supporting nested imports is too much of a problem, we could fallback on the copy-paste solution

[michelengelen]

should we add the mentioned PR as a fix for this @alexfauquette ?

[alexfauquette]

I will close the issue after checking the PR and the monorepo update correctly fixed it