-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
User story:
As a SPA developer, I want to get content in the correct format, so that I can use the content write away in my components without changing the component or massaging the data.
As a Magnolia developer, I want to run model code and return results of this code to the frontend components, so that I can solve more complex customer requirements such as serverside calculations.
Notes:
See: SPA - How to match content to API of JS components
Acceptance criteria:
- Control the 'format' of the content that is passed to a frontend component, such as property names, arrays vs maps, heirarchies.
- Run models and deliver content from them.
Notes:
If we added GraphQL support - it would be likely be a little file living next to each component to specify the props to get and their shape. Therefore, without GraphQL an alternative would be to support a "JSON transformer file", or a component model, which would specify or remap the default content, and supply it as a new JSON format. Possibly this could also be supplied as an FTL file to provide "templating the JSON response".
- relates to
-
MGNLREST-329 ReferenceResolver should provide access to component node and property name
- Accepted