Dynamic Data with New Controller Model (How is Dynamic Data effected? (We…
Dynamic Data with New Controller Model
Name for new controller?
Set to render a configured page in Hippo
This will replace the CPC in Crampon
How will Dynamic Data be configured?
Jake feels like this is cumbersome for non-tech people
Standalone tool that will allow a user to configure dynamic data. This will contains stuff like:
pre-populated list of values
all required options geared toward helping the users understand what we need
This will then convert this data to what Hippo needs to configure dynamic data in the Model doc type
Future: this could live in the Content Editior UI. But it's ok if it's standalone for now
How will dynamic data be represented in the modelData JSON blob?
Why was the PagesController created?
Not vue-specific based controller
site.common.include.model.json.default=true outputs modelData JSON blob to the bottom of the page
Previous/Current way to render is BE driven using Thymeleaf.
The new way injects JSON ModelData instead of HTML rendered content
Thymeleaf version: combines logic&FE, while the Vue Controller version clearly separates the two.
How is Dynamic Data effected?
Some of the dynamic data logic is specified to Thymeleaf (e.g.,
etc.). The new controller doesn't support this.
There's also the Dynamic Data feature we introduced in the components library
We won't know what data we need until the client request for a page.
No need to configure/use beans in the new impl
Current impl only allows GET w/o request body
we need a "data" object (or something similar) in the modeldata that belongs to the "dynamicData" property
Data = data returned given the dynamic data values
We need to figure out how to assign which dynamic data object goes to what FE piece on the page
Story for the FEDs/Architect
Application Josh wrote
Used to be static files in a repo
It's now updated to run as a standalone application that renders components.