feature suggestion: add inherited attributes to (all) struct members

[Morg42]

Imagine a configuration like

item1:
  type: foo
  struct: 
  - plugin1.struct1
  - my.file1.struct1

Now, for some reason or other, you want all struct items to be (e.g.) cached, databased or update-enforced or the like.

You could

• modify the plugins (or your own) struct definition
• copy a plugins struct definition to your own and modify
• add all struct items manually and add your attribute
• ...?

Suggestion:

item1:
  type: foo
  struct:
  - plugin1.struct1
  - my.file1.struct1
  struct_attrs:
    - database: init
    - enforce_updates: true

item2:
  type: foo
  struct:
  - plugin1.struct1
     - database: init
     - enforce_updates: true
  - my.file1.struct1

This would apply the given attributes (database and enforce_updates) to all struct items (item1) or the plugin1.struct1-items (item2) respectively.

The first variant is easier to read, but can only be applied to all structs; variant 2 is less easy to read and more error-prone considering the more complex formatting, but can be applied more differentiated.

Maybe even other ways of defining attributes come to mind...

[onkelandy]

I like the idea, would prefer the more granular variation as suggested in item2.

On the other hand, there is already the option to inherit attributes from a common parent object, isn't it? It would also be an option to adapt the plugin structs in such a way that there are always some sort of setting items that users can adjust individually. Most likely database and enforce_updates might suffice anyhow..?

[Morg42]

The second method would work if this was implemented by the plugin author - and only for the attributes so designated. While this would be the more aesthetic solution, it would require a lot of prethought. Maybe applying attributes of some other plugin (maybe not even written yet) will be needed?