[MGNLREST-547] Create sub Norsu endpoint definition for the NodeTypeResolver Created: 01/Nov/22 Updated: 14/Nov/22 Resolved: 14/Nov/22 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Canh Nguyen | Assignee: | Canh Nguyen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | 1.75d | Time Spent: | 1.75d |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||||||||||||||||||||||
| Template: | ||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
|||||||||||||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
|||||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
|||||||||||||||||||||||||||||||||||
| Epic Link: | Norsu delivery endpoint (phase 1) | |||||||||||||||||||||||||||||||||||
| Sprint: | DevX 23 | |||||||||||||||||||||||||||||||||||
| Story Points: | 3 | |||||||||||||||||||||||||||||||||||
| Team: | ||||||||||||||||||||||||||||||||||||
| Description |
|
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: pagesResolverV2 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. |