Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CONTENT] Create collapsible families of extensions #274

Open
gynt opened this issue Nov 13, 2024 · 3 comments
Open

[CONTENT] Create collapsible families of extensions #274

gynt opened this issue Nov 13, 2024 · 3 comments

Comments

@gynt
Copy link
Collaborator

gynt commented Nov 13, 2024

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.

Root extension:

name: extension-A
version: B
family:
- name: extension-A-family
  root: true

Family extension:

name: extension-A-files
version: B
family:
- name: extension-A-family
@Krarilotus
Copy link
Collaborator

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

@gynt
Copy link
Collaborator Author

gynt commented Dec 5, 2024

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?

@Krarilotus
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants