Thanks for adding a type label to the PR! 👍

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

Updated pages:

• docs/data/charts/axis/axis.md

Generated by 🚫 dangerJS against 2c242dc

CodSpeed Performance Report

Merging #17848 will not alter performance

_{Comparing bernardobelchior:grouped-axes (2c242dc) with master (ee34ca3)}

Summary

✅ 9 untouched benchmarks

I'm not very fond of the hack to make every third tick bigger than normal, but line elements' x and y properties cannot be styled using CSS.

Most of the time those exemples looks like their is a real axis (here the monthsand a fake one (quarters) for display purpose.

I'm wondering is instead of hacking a multiple axes system, we should provide a recipe about "This is how to create your custom axis".

I'm wondering is instead of hacking a multiple axes system, we should provide a recipe about "This is how to create your custom axis".

Depending on the result it might be simpler to have this demo instead of a custom axis.

I'm wondering is instead of hacking a multiple axes system, we should provide a recipe about "This is how to create your custom axis".

Yeah, I think we should, but I don't think that's a quick win. Looking at the work being done in ChartsXAxis, it seems like we need to encapsulate some logic into hooks and export them before we can create the docs.

If this is going to require a significant amount of effort, I don't think I can take this at the moment, so we need to decide whether we merge this demo, and pick this up later with the goal of creating a long-term solution for this problem.

What do you think?

Rather than showing how to create a custom GroupedAxis, should WE create it to simplify it up?

Though it might be overkill 🤔, as this is not a huge use-case.

😆

Rather than showing how to create a custom GroupedAxis, should WE create it to simplify it up?

You mean create it in the library and export it? I think it makes sense long term, but I'm already working on the toolbar and zoom, don't want to spread myself too thin 😅

Could you create an issue the different limitations and the solution found by other libraries to support this case. It could be a nice v9 feature?

Could you create an issue the different limitations and the solution found by other libraries to support this case. It could be a nice v9 feature?

Done: #17931