{"action":"created","issue":{"url":"https://api.github.com/repos/netlify/netlify-cms/issues/192","repository_url":"https://api.github.com/repos/netlify/netlify-cms","labels_url":"https://api.github.com/repos/netlify/netlify-cms/issues/192/labels{/name}","comments_url":"https://api.github.com/repos/netlify/netlify-cms/issues/192/comments","events_url":"https://api.github.com/repos/netlify/netlify-cms/issues/192/events","html_url":"https://github.com/netlify/netlify-cms/issues/192","id":196745974,"number":192,"title":"Dependency system for relation fields & editorial workflow.","user":{"login":"cassiozen","id":33676,"avatar_url":"https://avatars.githubusercontent.com/u/33676?v=3","gravatar_id":"","url":"https://api.github.com/users/cassiozen","html_url":"https://github.com/cassiozen","followers_url":"https://api.github.com/users/cassiozen/followers","following_url":"https://api.github.com/users/cassiozen/following{/other_user}","gists_url":"https://api.github.com/users/cassiozen/gists{/gist_id}","starred_url":"https://api.github.com/users/cassiozen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cassiozen/subscriptions","organizations_url":"https://api.github.com/users/cassiozen/orgs","repos_url":"https://api.github.com/users/cassiozen/repos","events_url":"https://api.github.com/users/cassiozen/events{/privacy}","received_events_url":"https://api.github.com/users/cassiozen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-12-20T18:33:25Z","updated_at":"2016-12-20T18:34:52Z","closed_at":null,"body":"Currently, the relation widget only display fields already published and available through search integration. \r\n\r\nBut the ideal flow should work like this:\r\n\r\n• the relations just work, whether something is published or not\r\n• So if the user is working on an \"event\" kind of entry\r\n• He/she can create new speakers, events, etc, and create the relations, everything marked as in progress in the editorial workflow\r\n• Once he/she do “Publish” for the event, the CMS notices that a bunch of relations are not ready to be published, and tells me those needs to be ready for publishing as well, once those are ready for publishing, I click “Publish” and the CMS tells me:\r\n\r\n```The following related items will be published together with \"New event for 2017\":\r\n\r\n* Cassio Zen (speaker)\r\n* The React Way (workshop)\r\n\r\nPublish all items now?\r\n````"},"comment":{"url":"https://api.github.com/repos/netlify/netlify-cms/issues/comments/268320941","html_url":"https://github.com/netlify/netlify-cms/issues/192#issuecomment-268320941","issue_url":"https://api.github.com/repos/netlify/netlify-cms/issues/192","id":268320941,"user":{"login":"cassiozen","id":33676,"avatar_url":"https://avatars.githubusercontent.com/u/33676?v=3","gravatar_id":"","url":"https://api.github.com/users/cassiozen","html_url":"https://github.com/cassiozen","followers_url":"https://api.github.com/users/cassiozen/followers","following_url":"https://api.github.com/users/cassiozen/following{/other_user}","gists_url":"https://api.github.com/users/cassiozen/gists{/gist_id}","starred_url":"https://api.github.com/users/cassiozen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cassiozen/subscriptions","organizations_url":"https://api.github.com/users/cassiozen/orgs","repos_url":"https://api.github.com/users/cassiozen/repos","events_url":"https://api.github.com/users/cassiozen/events{/privacy}","received_events_url":"https://api.github.com/users/cassiozen/received_events","type":"User","site_admin":false},"created_at":"2016-12-20T18:34:52Z","updated_at":"2016-12-20T18:34:52Z","body":"Thoughts on how to implement this:\r\n\r\nFrom the point of view of architecture, I can create a new metadata field for unpublished entries, something like `dependencies`\r\n\r\nAnd when we try to publish, it would check all the dependency three to see which ones were not published yet…\r\n\r\nObs.:  Since metadata exists as long as the entry is on “unpublished” state, we will need to validate across metadata AND published entries. (And maybe throw an error if the entry wasn’t found in any)\r\n"}}
{"actor":{"display_login":"cassiozen"}}