{"action":"created","issue":{"url":"https://api.github.com/repos/stefanoverna/wishlist/issues/35","repository_url":"https://api.github.com/repos/stefanoverna/wishlist","labels_url":"https://api.github.com/repos/stefanoverna/wishlist/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/stefanoverna/wishlist/issues/35/comments","events_url":"https://api.github.com/repos/stefanoverna/wishlist/issues/35/events","html_url":"https://github.com/stefanoverna/wishlist/issues/35","id":322602076,"number":35,"title":"Hierarchical collections","user":{"login":"stefanoverna","id":51573,"avatar_url":"https://avatars0.githubusercontent.com/u/51573?v=4","gravatar_id":"","url":"https://api.github.com/users/stefanoverna","html_url":"https://github.com/stefanoverna","followers_url":"https://api.github.com/users/stefanoverna/followers","following_url":"https://api.github.com/users/stefanoverna/following{/other_user}","gists_url":"https://api.github.com/users/stefanoverna/gists{/gist_id}","starred_url":"https://api.github.com/users/stefanoverna/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stefanoverna/subscriptions","organizations_url":"https://api.github.com/users/stefanoverna/orgs","repos_url":"https://api.github.com/users/stefanoverna/repos","events_url":"https://api.github.com/users/stefanoverna/events{/privacy}","received_events_url":"https://api.github.com/users/stefanoverna/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-05-13T15:13:33Z","updated_at":"2018-05-13T15:13:38Z","closed_at":null,"author_association":"OWNER","body":" \n DatoCMS already allows records to be sorted manually with drag &amp; drop. The next logical step would be to allow the creation of a \"tree\" of records. \n \n\n-----\n\nOriginally posted by support@datocms.com"},"comment":{"url":"https://api.github.com/repos/stefanoverna/wishlist/issues/comments/388634171","html_url":"https://github.com/stefanoverna/wishlist/issues/35#issuecomment-388634171","issue_url":"https://api.github.com/repos/stefanoverna/wishlist/issues/35","id":388634171,"user":{"login":"stefanoverna","id":51573,"avatar_url":"https://avatars0.githubusercontent.com/u/51573?v=4","gravatar_id":"","url":"https://api.github.com/users/stefanoverna","html_url":"https://github.com/stefanoverna","followers_url":"https://api.github.com/users/stefanoverna/followers","following_url":"https://api.github.com/users/stefanoverna/following{/other_user}","gists_url":"https://api.github.com/users/stefanoverna/gists{/gist_id}","starred_url":"https://api.github.com/users/stefanoverna/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stefanoverna/subscriptions","organizations_url":"https://api.github.com/users/stefanoverna/orgs","repos_url":"https://api.github.com/users/stefanoverna/repos","events_url":"https://api.github.com/users/stefanoverna/events{/privacy}","received_events_url":"https://api.github.com/users/stefanoverna/received_events","type":"User","site_admin":false},"created_at":"2018-05-13T15:13:38Z","updated_at":"2018-05-13T15:13:38Z","author_association":"OWNER","body":" \n Right, but what I'm thinking is that the Tree field could actually affect a field on the Page record—so if I take a Page record with a slug of 'foo' and nest it in my Tree model under a label of 'bar', that record would now have a permalink field with a value of 'bar/foo'. But maybe this is really a larger topic, as essentially it's about routing, and one would also want to be able to implement rule-based routing e.g.  for \"Post\" types, and also right now \"routing\" as such is rather done in the 'dump' script process... I'm not sure how one would keep all those things in sync \n \n\n-----\n\nOriginally posted by lunelson@gmail.com"}}
{"actor":{"display_login":"stefanoverna"}}