Support higher-order "compositions" #129
Description
Support "compositions" that are higher-order components (groups?) referring to nested elements.
This would enable creating for example a Form that would contain elements (Button, Heading, Paragraph). Currently, this needs to be manually puzzled together, as is currently done in the Figmagic example https://github.com/mikaelvesavuori/figmagic-example).
Supporting this is probably a pretty significant undertaking as elements need to be enumerated (and generated?) before-hand, so these can be referenced in the higher-order component ("Form", in the above example). Because this also lacks a conceptual model in Figmagic, there will certainly be other parts of the source code that need to be adjusted.
Success criteria:
- The solution should follow the overall, general standards
- As far as any new concepts go, these should stay consistent with the general domain model that is outlined
- The solution requires good testing, ideally (near-) full coverage of additions
- Any user APIs should stay unpolluted and unharmed, and new additions should stay consistent with existing language etc