Details
-
Epic
-
Resolution: Fixed
-
P2: Important
-
QDS 2.2.0
-
None
-
Variant Support
-
QDS 2D - 2021 Week 43/44, QDS Berlin - 2021 Week 49/51
Description
Research how to implement proper variant support to be able to create vanilla release and change customization just by switching the variant.
Areas to study:
- Support State Syntax
- Detect if a State Variant is found in the Variant name syntax
- If a State Variant is found keep track of id’s in each Variant
- If id’s match keep track of property changes
- Create States in qds and apply property changes to the correct State
- If a merge template is known (Button) and a state is know (Hover) add the correct when condition
- Detect if Theme Variant is found in the Variant name syntax
- If Theme Variant is found and Colours use the Style name, keep track of which theme is applied
- Apply the correct id in each case, or apply the appended id generated in creating the library style
- Detect if another non-qml Variant is defined (Brand)
- Keep track of id’s and property changes between id’s
- Either a) creates states with Variants full syntax
(Brand=QDS > brand-qds and Brand=Creator > brand-creator)
Or b) Create Components with variants value appended.
Attachments
Issue Links
- depends on
-
QDS-5978 Export the states array of the component from Figma
- Closed
-
QDS-5979 Update asset importer to generate States
- Closed
- is duplicated by
-
QDS-5453 Support for Figma variants
- Closed
-
QDS-5275 Make States more like Figma variants
- Open
-
QDS-3340 varients create new components - states would be ideal
- Closed
-
QDS-3739 Research: Add a means to export multiple states of a component into one QML component
- Closed
-
QDS-4579 State management for components
- Closed
- relates to
-
QDS-6654 Document the Variant import/export
- Closed
-
QDS-4579 State management for components
- Closed
-
QDS-5760 Create JS package to compare two metadata files.
- Closed