Skip to content

Route context match is not validated for child entities #48

@simonbaese

Description

@simonbaese

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions