redoing config structure mods and features about alpacka

[copygirl]

Should it be possible to nest these?

mods:

  common:
    - foo

  server:
    defaults: side: server
    list:
      - foo

  client:
    defaults: side: client
    list:
      - foo
    optional:
      defaults:
        feature: optional
        version: latest
      list:
        - foo

What about providing common default list names, or defining them beforehand?

defaults:
  version: recommended
  client: side: client
  server: side: server
  optional: feature: optional
  latest: version: latest

mods:
  common:
    - foo
    - bar
  client: ...
  server: ...
  client & optional: ...
  server & optional & latest: ...

Named lists like Tweaks and Utilities would be useful, but you can always use a comment, too?

[NikkyAI]

yes you can create a comment but... i want to have the name be the key in the dictionary
because we cannot get the values of yaml comments obviously

i like them to be grouped with their defaults
providing the defaults for all list names has a bit less indentation in the lists.. which i did not like about my proposed format

being able to nest lists.. i'd rather not.. that will be a mess in code

linking them with '&' looks cool.. if you can implement that it would be awesome
but what if two of the lists define the same defaults.. which one takes precendence ?
i would say right to left.. making the leftmost (server in server & optional & latest) the most significant