- Issue created by @just_like_good_vibes
- 🇫🇷France Grimreaper France 🇫🇷
Thanks for opening the issue.
As discussed this would definitively takes its place in ui_styles_page. I was not aware of the possibility to make distinction by routes, I first imagine a global setting like with ui_styles_entity_status to keep stuff simple.
Also putting classes on the body tag makes me think of the theme feature of ui_skins. Maybe this overlap?
But a mechanism that will allow to have different values based on the context I think it is something to be done for ui_styles and ui_skins then.
And I think such mechanism is a "source" plugin system so you could have your source plugin in which you put (configurable or not, as desired) the logic of, for this route I want those styles, for this one I want those styles, etc. Maybe with some kind of weight and a isApplicable method? And in this case it makes me think more about service tag and service collector.