For now, most of the classes are set on the smallest component. The historical reason is the element state. To know when we need to set barLabelClasses.highlighted we need to get the highlight.

THis lead to a quickly growing number of classes objects. For example the bar chart has

• barLabelClasses for the labels
• barElementClasses for the rectangles
• barClasses for the groups in the BarPlot

We can reconsider how the classes are structured to simplify the selector creation.

We could maybe have one useUtilistyClasses per component when the classes generation relies on the component state. But a single class object exported per folder.