-
Improvement
-
Resolution: Done
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
DevX 23
-
0
NorsuEndpointDefinition introduces a new property to configure mapping node types with NodeTypeResolver implementation classes. To simplify the config, we need to introduce a sub definition for NodeTypeResolver so we can config nodeTypeMappings like below:
$type: deliverEndpoint_v2 workspace: "" rootPath: "/" depth: 10 nodeTypeMappings: pages: nodeType: "mgnl:page" $type: pagesResolver_v2 tours: $type: customTourDataResolver includeSystemProperties: true systemProperties: - mgnl:type - mgnl:created - mgnl:template referenceDepth: 2 references: - name: norsuCombo propertyName: norsuCombo referenceResolver: $type: norsuReferenceResolver - name: image propertyName: image referenceResolver: $type: assetReferenceResolver assetRenditions: - '480' - 1600x1200 - name: destinations propertyName: destination referenceResolver: $type: jcrReferenceResolver targetWorkspace: category
nodeType could be optional, pagesResolverV2 will have a default nodeType. But we can configure pagesResolverV2 with other compatible node types.
- clones
-
-
- Closed
-
- is depended upon by
-
PAGES-922 LegacyPageWriter ignores page properties
-
- Closed
-
- to be documented by
-
PAGES-929 DOC: PageNodeTypeResolverDefinition and pre-configured PagesNorsuDeliveryEndpointDefinition
-
- Closed
-
1.
|
Implementation |
|
Completed | Canh Nguyen |
2.
|
Review |
|
Completed | Dai Ha |
3.
|
Pre-Integration QA |
|
Completed | Dai Ha |
4.
|
QA |
|
Completed | Robert Šiška |
