[MGNLREST-618] DOC: Example where reference resolver is configured but without depthInReferencedNode property Created: 24/Jan/23 Updated: 03/May/23 Resolved: 03/May/23 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Martin Drápela | Assignee: | Martin Drápela |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Story Points: | 2 | ||||||||
| Team: | |||||||||
| Work Started: | |||||||||
| Description |
|
This is a Add between 1. a .2. a case where a resolver is configured, but without the depthInReferencedNode property. Try to recreate using the tour-finder case present there.
|
| Comments |
| Comment by Christopher Zimmermann [ 03/May/23 ] |
|
Close as Obsolete because it is a bad practice not to use the depthInReferencedNode property - so its clerer for the customers to see what is the right thing to do. |