Quick question on using Page Includes in Spark. In V1, loading multiple instances of a page include creates model collisions, so we avoid using includes in components such as drawers and decks. Basically what happens is each page include instance has the same model name and then when you work across multiple includes, Skuid gets confused on which copy of the model to reference.
V2 looks to have much more specific namespacing controls. Has this model conflict behavior been updated in Spark?
The use case I have is that I have some design patterns to display a task record a certain way, but there are variations on the pattern depending on the type of task it is. I would like to make these variants as pages to be used as page include components and use them in a deck. We have a lookup to the Skuid_Page object on the task to determine which page to use for the specific task display. Here’s the basic logic on the page structure I’m thinking about:
Deck
Deck Item 1 (Task 1 calls for Page Include A to be used and sends the id parameter into Page A)
Deck Item 2 (Task 2 calls for Page Include B to be used and sends the id parameter into Page B)
Deck Item 3 (Task 3 calls for Page Include A to be used and sends the id parameter into Page A) - Will the model on this include collide with include in Deck Item 1 like it would in the V1 API?
As a side note, the page builder requires a selection of the page when configuring the page include component, however you can make dynamic page includes by editing the XML and using merge syntax in place of the page name. I don’t know if this is supported, but it’s pretty slick.
