{"action":"created","issue":{"url":"https://api.github.com/repos/endpoints/ember-data-endpoints/issues/9","labels_url":"https://api.github.com/repos/endpoints/ember-data-endpoints/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/endpoints/ember-data-endpoints/issues/9/comments","events_url":"https://api.github.com/repos/endpoints/ember-data-endpoints/issues/9/events","html_url":"https://github.com/endpoints/ember-data-endpoints/issues/9","id":56429307,"number":9,"title":"support nested relations?","user":{"login":"tkellen","id":1004324,"avatar_url":"https://avatars.githubusercontent.com/u/1004324?v=3","gravatar_id":"","url":"https://api.github.com/users/tkellen","html_url":"https://github.com/tkellen","followers_url":"https://api.github.com/users/tkellen/followers","following_url":"https://api.github.com/users/tkellen/following{/other_user}","gists_url":"https://api.github.com/users/tkellen/gists{/gist_id}","starred_url":"https://api.github.com/users/tkellen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tkellen/subscriptions","organizations_url":"https://api.github.com/users/tkellen/orgs","repos_url":"https://api.github.com/users/tkellen/repos","events_url":"https://api.github.com/users/tkellen/events{/privacy}","received_events_url":"https://api.github.com/users/tkellen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-02-03T20:06:04Z","updated_at":"2015-05-01T13:58:27Z","closed_at":null,"body":"Some context:\r\nIn this example,  an organization has projects and a project has phases. Sometimes, a user may wish to see the organization related to the phase, but not want the intermediate project record in the response. \r\nThis can be accomplished using endpoints with the following:\r\n\r\n`GET /project-phases/12?include=project.organizations`\r\n\r\n```js\r\n{\r\n  \"linked\": {\r\n    \"organizations\": [\r\n      {\r\n        \"id\": 12,\r\n        \"name\": \".....\",\r\n      }\r\n    ]\r\n  },\r\n  \"project-phases\": {\r\n    \"id\": 1,\r\n    \"name\": \"Phase One\",\r\n    \"project_id\": 25,\r\n    \"first_day\": \"2014-04-21T04:00:00.000Z\",\r\n    \"last_day\": \"2014-12-22T05:00:00.000Z\",\r\n    \"links\": {\r\n      \"project.organization\": {\r\n        \"type\": \"organizations\",\r\n        \"id\": 12\r\n      }\r\n    }\r\n  }\r\n}\r\n```\r\n\r\nIs supporting this even possible with ember-data @bmac?"},"comment":{"url":"https://api.github.com/repos/endpoints/ember-data-endpoints/issues/comments/98139921","html_url":"https://github.com/endpoints/ember-data-endpoints/issues/9#issuecomment-98139921","issue_url":"https://api.github.com/repos/endpoints/ember-data-endpoints/issues/9","id":98139921,"user":{"login":"bmac","id":54056,"avatar_url":"https://avatars.githubusercontent.com/u/54056?v=3","gravatar_id":"","url":"https://api.github.com/users/bmac","html_url":"https://github.com/bmac","followers_url":"https://api.github.com/users/bmac/followers","following_url":"https://api.github.com/users/bmac/following{/other_user}","gists_url":"https://api.github.com/users/bmac/gists{/gist_id}","starred_url":"https://api.github.com/users/bmac/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bmac/subscriptions","organizations_url":"https://api.github.com/users/bmac/orgs","repos_url":"https://api.github.com/users/bmac/repos","events_url":"https://api.github.com/users/bmac/events{/privacy}","received_events_url":"https://api.github.com/users/bmac/received_events","type":"User","site_admin":false},"created_at":"2015-05-01T13:58:27Z","updated_at":"2015-05-01T13:58:27Z","body":"@leobalter I disagree. The logic for building the urls should live in the server. It makes it easier to change that logic or update the url in the future without also requiring a change in the client."}}