At the moment the only method prototypes have of creating logic is from a defined set of Component provided to them via a library.
This becomes difficult to deal with when it is necessary to associate logic between components.
There should therefore be a feature implemented cross-cutting several tooling exports that will add this functionality. This can be done by allowing the creation of components that will serve as test components that are not exported but viewable.
Use cases
A project in Creator may have a button that triggers a state change such as opening a flyout
A scenario in the Component Explorer may have a button that triggers the hide/show of a modal dialog
A project in Creator may need to pass arbitrary data from a root location such as language
A project in Creator may need to provide data from an external API
A scenario in the Component Explorer that requires a component created by the user to be shown for documentation purposes
Affected exports
mapDataToComponents
This function would now need to interpret the extra logic needed to complete the functionality mapping. An open question would be how do plugins fit in, should strings represent the logic with the use of Function?
mapDataToCodePreview
This function may need to be re-evaluated so that the strings can be editable. This would provide the surface to edit the string above but would come with certain risks.
Data structure
The data structure of project files may need to be evaluated
Abstract
At the moment the only method prototypes have of creating logic is from a defined set of Component provided to them via a library.
This becomes difficult to deal with when it is necessary to associate logic between components.
There should therefore be a feature implemented cross-cutting several tooling exports that will add this functionality. This can be done by allowing the creation of components that will serve as test components that are not exported but viewable.
Use cases
Affected exports
mapDataToComponentsThis function would now need to interpret the extra logic needed to complete the functionality mapping. An open question would be how do plugins fit in, should strings represent the logic with the use of Function?mapDataToCodePreviewThis function may need to be re-evaluated so that the strings can be editable. This would provide the surface to edit the string above but would come with certain risks.Data structure