On Tue, Aug 4, 2015 at 11:35 AM, [email protected] <[email protected]> wrote:
Hi devs,
When we create a new page through Add > Page (for example) we are still setting the parent ATM, even though it’s not used by default in the breadcrumb or elswhere.
Question 1: do we still want to set it or should we stop doing that when core.hierarchyMode=reference? Question 2: do we still want to enforce having a parent set in our build?
My preference would to not change any in the 7.x cycle (i.e. keep setting the parent when creating new pages and keep enforcing parents in the build). The rationale is that: * 7.x is a transition cycle for Nested Spaces/Documents so it’s good to observe how users are using them * We should not use Nested Documents in our apps in the 7.x cycle as this would cause potential breakages in existing extensions since we would change location of wiki pages. IMO we need to implement aliases before we start doing so, but not before 8.x.
WDYT?
* 1: yes, lets move the discussion about that when working on 8.x (and even I think I will vote for keeping the behavior as long as the concept of parent exist in the API) * 2: no, there is not reason to force it anymore IMO. It's not like having a document without a parent was a technical issue anyway.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne