{"action":"opened","issue":{"url":"https://api.github.com/repos/joukevandermaas/saule/issues/208","repository_url":"https://api.github.com/repos/joukevandermaas/saule","labels_url":"https://api.github.com/repos/joukevandermaas/saule/issues/208/labels{/name}","comments_url":"https://api.github.com/repos/joukevandermaas/saule/issues/208/comments","events_url":"https://api.github.com/repos/joukevandermaas/saule/issues/208/events","html_url":"https://github.com/joukevandermaas/saule/issues/208","id":370511588,"node_id":"MDU6SXNzdWUzNzA1MTE1ODg=","number":208,"title":"Relationship paths in include not supported","user":{"login":"PhyberApex","id":1316500,"node_id":"MDQ6VXNlcjEzMTY1MDA=","avatar_url":"https://avatars3.githubusercontent.com/u/1316500?v=4","gravatar_id":"","url":"https://api.github.com/users/PhyberApex","html_url":"https://github.com/PhyberApex","followers_url":"https://api.github.com/users/PhyberApex/followers","following_url":"https://api.github.com/users/PhyberApex/following{/other_user}","gists_url":"https://api.github.com/users/PhyberApex/gists{/gist_id}","starred_url":"https://api.github.com/users/PhyberApex/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/PhyberApex/subscriptions","organizations_url":"https://api.github.com/users/PhyberApex/orgs","repos_url":"https://api.github.com/users/PhyberApex/repos","events_url":"https://api.github.com/users/PhyberApex/events{/privacy}","received_events_url":"https://api.github.com/users/PhyberApex/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-16T09:08:48Z","updated_at":"2018-10-16T09:08:48Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"As stated [https://jsonapi.org/format/#fetching-includes](here) in the JSON API specification. A nested releationship should be included and the dot should be used as a path seperator for such includes.\r\n\r\nCurrently Saule does not implement this and does not respond with the needed 400 Bad Request message if such an path is encountered.\r\n\r\nSame as the other issues I opened. If I find the spare time I would like to open a PR for that.\r\n\r\n~Cheers"}}
{"actor":{"display_login":"PhyberApex"}}