You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We've been using nested sets (through using the folder divider / structure when creating new sets). This has been working well organisation wise as we can have "components", "brand" overrides for whitelabeling, and translations all separate and toggle on an off the required ones
I'm now in the mist of migrating our current "component" set and breaking it down to sub pages -- mirroring to our design system components. Ie. "Badge" and "Flagbox" in the screenshot below.
However, what I've found is every time I create a new sub set (ie. component/❖ Something new) I would need to tweak the themes file to enable that particular one.
This is normally fine if it's just 1 theme, but we've got 10+ themes... which means going in and enabling it for each of them manually.
Describe the solution you'd like
It would be nice to have have the option to set Disabled/Reference/Enabled for the parent set. So in this example I would set it in the component parent set and all the sub ones (Badge, Flagbox, and future created ones) will be enabled automatically.
(alternatively, something similar to wildcard folder structures used in code could potentially work... component/**/*-esk)
And if I have different sub set settings (ie. "brand" group set in the above screenshot), then the parent setting won't be applied.
Describe alternatives you've considered
Manually tweaking the theme file every single time new sub set is created.
Additional context
The way I can quickly select all or partial select in the sidebar is a similar UX to what I'd be keen to have when configuring sets within themes.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We've been using nested sets (through using the folder divider
/
structure when creating new sets). This has been working well organisation wise as we can have "components", "brand" overrides for whitelabeling, and translations all separate and toggle on an off the required onesI'm now in the mist of migrating our current "component" set and breaking it down to sub pages -- mirroring to our design system components. Ie. "Badge" and "Flagbox" in the screenshot below.
However, what I've found is every time I create a new sub set (ie.
component/❖ Something new
) I would need to tweak the themes file to enable that particular one.This is normally fine if it's just 1 theme, but we've got 10+ themes... which means going in and enabling it for each of them manually.
Describe the solution you'd like
It would be nice to have have the option to set Disabled/Reference/Enabled for the parent set. So in this example I would set it in the
component
parent set and all the sub ones (Badge, Flagbox, and future created ones) will be enabled automatically.(alternatively, something similar to wildcard folder structures used in code could potentially work...
component/**/*
-esk)And if I have different sub set settings (ie. "brand" group set in the above screenshot), then the parent setting won't be applied.
Describe alternatives you've considered
Manually tweaking the theme file every single time new sub set is created.
Additional context
The way I can quickly select all or partial select in the sidebar is a similar UX to what I'd be keen to have when configuring sets within themes.
The text was updated successfully, but these errors were encountered: