Hello everyone,
we recently noticed while working on the pinned child pages feature that the /children REST resources is currently still using by default the old parent/child relationship by default.
@mflorea improved the API to allow specifying a parameter to use the reference (nested page) relation which is the default in XWiki since 7.2.
Now IMO the /children REST resources should always follow the configuration core.hierarchyMode
specified in xwiki.properties and which uses reference
by default. I don’t see a good reason to keep having this resource returning by default answers using a mode that is long deprecated now.
So my proposal here is to:
- Break the REST API behaviour to always rely on the
core.hierarchyMode
configuration to know which mode to use - Ensure to provide a parameter allowing to force the model to use either parent/child or nested, without relying on
core.hierarchyMode
: any extension relying on the current behaviour could modify without much change the URLs to use this parameter.
I tried to search for /children
in xwiki-contrib: we have a few hits but not that much: Code search results · GitHub
I propose to perform those changes only in master.
I’m opening this vote for 2 weeks, until 10th June 2024.
Here’s my +1.