[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: PNG File image-2023-01-24-12-23-25-636.png    
Issue Links:
Relates
relates to MGNLREST-604 DOC: New depthInReferencedNode property Closed
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: DeveloperX
Work Started:

 Description   

This is a MGNLREST-604 follow-up.

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.

Generated at Mon Feb 12 07:01:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.