A child entity path looks something like this:
/grand-parent/{{grand-parent-id}}/parent/{{parent-id}}/child-entity/{{child-id}}
This way we can easily access related ("ancestor") entities when handling a child entity. See the some academy entities for example. A Course has Lectures which have Paragraphs which have Questions.
When accessing the route though we have the perspective of the child entity. Therefore the entity of {{child-id}} is loaded. Therefore, we could also access the child entity via some other path, e.g.:
/grand-parent/{{grand-parent-id}}/parent/{{some-other-parent-id}}/child-entity/{{child-id}}
There needs to be a validation for the route that the entities are actually related. That will help to build reliable bread crumbs for example.
A child entity path looks something like this:
/grand-parent/{{grand-parent-id}}/parent/{{parent-id}}/child-entity/{{child-id}}This way we can easily access related ("ancestor") entities when handling a child entity. See the some academy entities for example. A
CoursehasLectureswhich haveParagraphswhich haveQuestions.When accessing the route though we have the perspective of the child entity. Therefore the entity of
{{child-id}}is loaded. Therefore, we could also access the child entity via some other path, e.g.:/grand-parent/{{grand-parent-id}}/parent/{{some-other-parent-id}}/child-entity/{{child-id}}There needs to be a validation for the route that the entities are actually related. That will help to build reliable bread crumbs for example.