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
Proposal
Modify definition.yml to include a family: field that can list the family of extensions it belongs to. This way, we can collapse extensions of the same family into one display node. The family needs to define a root extension that will be the one for display purposes. And if nothing is uncollapsed then this root is activated upon click.
I am just not sure exactly which problem that solves. In which way.
-> If we have these families, what will be the functional benefit, if they collapse, how do they interact besides this collapse, and can i really expect to activate a 'family' by itself? Would that be the default config of that family?
-> can you define the scope of what could be a family? Like make some examples? :D
I am just not sure exactly which problem that solves. In which way. -> If we have these families, what will be the functional benefit, if they collapse, how do they interact besides this collapse, and can i really expect to activate a 'family' by itself? Would that be the default config of that family? -> can you define the scope of what could be a family? Like make some examples? :D
Is this still relevant after we discussed on Discord?
No, actually i understand now how your family plan works and i find it good combined with the ability to add multiple folders for multiple extensions into one git repository
Proposal
Modify definition.yml to include a
family:
field that can list the family of extensions it belongs to. This way, we can collapse extensions of the same family into one display node. The family needs to define aroot
extension that will be the one for display purposes. And if nothing is uncollapsed then this root is activated upon click.Root extension:
Family extension:
The text was updated successfully, but these errors were encountered: