{"action":"created","issue":{"url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/292","repository_url":"https://api.github.com/repos/OrchardCMS/Orchard2","labels_url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/292/labels{/name}","comments_url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/292/comments","events_url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/292/events","html_url":"https://github.com/OrchardCMS/Orchard2/issues/292","id":185542271,"number":292,"title":"Validate part drivers","user":{"login":"jtkech","id":8586360,"avatar_url":"https://avatars.githubusercontent.com/u/8586360?v=3","gravatar_id":"","url":"https://api.github.com/users/jtkech","html_url":"https://github.com/jtkech","followers_url":"https://api.github.com/users/jtkech/followers","following_url":"https://api.github.com/users/jtkech/following{/other_user}","gists_url":"https://api.github.com/users/jtkech/gists{/gist_id}","starred_url":"https://api.github.com/users/jtkech/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jtkech/subscriptions","organizations_url":"https://api.github.com/users/jtkech/orgs","repos_url":"https://api.github.com/users/jtkech/repos","events_url":"https://api.github.com/users/jtkech/events{/privacy}","received_events_url":"https://api.github.com/users/jtkech/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-10-27T00:08:33Z","updated_at":"2016-10-27T00:48:41Z","closed_at":null,"body":"Sorry no time right now to retrieve the details and how it can fit in O2.\r\n\r\n- But, when submitting a content item form, the idea is to have the ability to `Validate` model values of all parts without any database writing, this before creating and / or updating a content item.\r\n\r\n- As an example, in O1, we are using a workaround to reduce transaction logs related to comment submissions through the front end (then we also needed to adapt the audit trail module).\r\n\r\n- Also have a content type `Versioned` option. Then, when publishing, if this option is set a new content item version is created, otherwise the current version is updated.\r\n\r\nBest."},"comment":{"url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/comments/256517575","html_url":"https://github.com/OrchardCMS/Orchard2/issues/292#issuecomment-256517575","issue_url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/292","id":256517575,"user":{"login":"sebastienros","id":1165805,"avatar_url":"https://avatars.githubusercontent.com/u/1165805?v=3","gravatar_id":"","url":"https://api.github.com/users/sebastienros","html_url":"https://github.com/sebastienros","followers_url":"https://api.github.com/users/sebastienros/followers","following_url":"https://api.github.com/users/sebastienros/following{/other_user}","gists_url":"https://api.github.com/users/sebastienros/gists{/gist_id}","starred_url":"https://api.github.com/users/sebastienros/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sebastienros/subscriptions","organizations_url":"https://api.github.com/users/sebastienros/orgs","repos_url":"https://api.github.com/users/sebastienros/repos","events_url":"https://api.github.com/users/sebastienros/events{/privacy}","received_events_url":"https://api.github.com/users/sebastienros/received_events","type":"User","site_admin":false},"created_at":"2016-10-27T00:48:41Z","updated_at":"2016-10-27T00:48:41Z","body":"I think everything is already handled, in O2 a content item is already a version. And none is created if the object is not valid, but I need to validate it as I haven't tried for a while. I agree with the concern.\r\n\r\nI don't understand the `Versioned` requirement. How is that different from `Draftable` in O1?"}}
{"actor":{"display_login":"sebastienros"}}