ditto Pat on the depends on when you ask.
In your consideration of when Skuid needs to reevaluate the snippet it will eventually be both.However our proof of concept will likely just use model/Row data . (The external data would more likely be the templates- the components to be rendered map). The trigger would be a state generated on the page. We are using this to accommodate a myriad set of vendor catalogs that don’t conform to any one format well.
So, the criteria might be what “mode” is the user operating in (that could be button or passed in from page include), the other would be which catalog or manufacturer it is.
The configuration permutations will be too big and variable to do component by component with declarative options.
For my purposes, to start, if the context could consist of id of component that called it that would be great.
Sorry that’s convoluted. I can provide workflow if necessary. Thanks
