[ 
http://jira.magnolia-cms.com/browse/MGNLDATA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24944#action_24944
 ] 

Boris Kraft commented on MGNLDATA-88:
-------------------------------------

Thanks. Meanwhile I saw the docs. I think the initial example should be more 
intuitive. When I first saw it it was immediately clear to me that the sample 
hierarchy must be wrong. That is not the feeling I want to give people when 
they look at the sample - and they should not need to read the docs to 
understand it.

I suggest that we rethink the example. We can always make more complex ones in 
the docs.

> Samples for hierarchical data types have incorrect hierarchy
> ------------------------------------------------------------
>
>                 Key: MGNLDATA-88
>                 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-88
>             Project: Magnolia Data Module
>          Issue Type: Bug
>         Environment: Magnolia 4.2 RC 2
>            Reporter: Boris Kraft
>            Assignee: Philipp Bärfuss
>
> The samples for the hierarchy ("Big-Flower-Inc") seem to have the wrong 
> hierarchy.
> The defined hierarchy is as follows:
> Company
> * Employees
> ** Developer
> ** Director
> ** Manager
> * Department
> As you can see, this doesn't allow to create employees within a department.
> It would make more sense to have the following hierarchy:
> Company
> * Department
> ** Employees
> *** Developer
> *** Director
> *** Manager
> The sample content should also reflect this different structure.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to