{"action":"created","issue":{"url":"https://api.github.com/repos/springload/wagtaildraftail/issues/64","repository_url":"https://api.github.com/repos/springload/wagtaildraftail","labels_url":"https://api.github.com/repos/springload/wagtaildraftail/issues/64/labels{/name}","comments_url":"https://api.github.com/repos/springload/wagtaildraftail/issues/64/comments","events_url":"https://api.github.com/repos/springload/wagtaildraftail/issues/64/events","html_url":"https://github.com/springload/wagtaildraftail/issues/64","id":310010830,"node_id":"MDU6SXNzdWUzMTAwMTA4MzA=","number":64,"title":"Provide upgrade path to Wagtail 2.0","user":{"login":"loicteixeira","id":6834938,"node_id":"MDQ6VXNlcjY4MzQ5Mzg=","avatar_url":"https://avatars3.githubusercontent.com/u/6834938?v=4","gravatar_id":"","url":"https://api.github.com/users/loicteixeira","html_url":"https://github.com/loicteixeira","followers_url":"https://api.github.com/users/loicteixeira/followers","following_url":"https://api.github.com/users/loicteixeira/following{/other_user}","gists_url":"https://api.github.com/users/loicteixeira/gists{/gist_id}","starred_url":"https://api.github.com/users/loicteixeira/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/loicteixeira/subscriptions","organizations_url":"https://api.github.com/users/loicteixeira/orgs","repos_url":"https://api.github.com/users/loicteixeira/repos","events_url":"https://api.github.com/users/loicteixeira/events{/privacy}","received_events_url":"https://api.github.com/users/loicteixeira/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":19,"created_at":"2018-03-30T08:40:52Z","updated_at":"2018-11-28T00:44:01Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Now that it is merged into Wagtail 2.0, there's little point in updating this package compatibility. Instead, provide an upgrade path since since are handled a bit differently."},"comment":{"url":"https://api.github.com/repos/springload/wagtaildraftail/issues/comments/442274751","html_url":"https://github.com/springload/wagtaildraftail/issues/64#issuecomment-442274751","issue_url":"https://api.github.com/repos/springload/wagtaildraftail/issues/64","id":442274751,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MjI3NDc1MQ==","user":{"login":"mojeto","id":5433957,"node_id":"MDQ6VXNlcjU0MzM5NTc=","avatar_url":"https://avatars1.githubusercontent.com/u/5433957?v=4","gravatar_id":"","url":"https://api.github.com/users/mojeto","html_url":"https://github.com/mojeto","followers_url":"https://api.github.com/users/mojeto/followers","following_url":"https://api.github.com/users/mojeto/following{/other_user}","gists_url":"https://api.github.com/users/mojeto/gists{/gist_id}","starred_url":"https://api.github.com/users/mojeto/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mojeto/subscriptions","organizations_url":"https://api.github.com/users/mojeto/orgs","repos_url":"https://api.github.com/users/mojeto/repos","events_url":"https://api.github.com/users/mojeto/events{/privacy}","received_events_url":"https://api.github.com/users/mojeto/received_events","type":"User","site_admin":false},"created_at":"2018-11-28T00:44:01Z","updated_at":"2018-11-28T00:44:01Z","author_association":"MEMBER","body":"This migration is becoming really painful. I'll need to find a way to remap wagtaildraftail `IMAGE` feature data to Wagtail `embed[embedtype=\"image\"]` feature that uses different keys for `altText` and `alignment` values before it can be converted from json to db html presentation.\r\n\r\nI understand the draftail content state json is converted to db html string for backward compatibility reason. As you @loicteixeira mentioned earlier with wagtaildraftail rich text we have possibilities to control wagtail admin part of feature and final front-end user html part of feature. The inner content state in json contains all the state data feature needs and it isn't in developer's main interest. Now we need to convert all our features data to db html string and back to json - and that is a lot of work. The db html **can't** be fron-end user html as it's main responsibility is to keep all the data feature needs (including the data for feature internal use and not to be displayed to end user). The feature db html code has to be unique enough so it can be easily parsed back to proper draftail feature also.\r\n\r\nAll that means we have to create json -> db html converter and back to replicate work that was done for us by content state json. In addition we have to create converters for the db html -> front end user html for advance features and or to remove internal feature data. All of that has to be done to keep the same functionality we already have. It doesn't help that `expand_db_html` action in Wagtail isn't implemented in a way to be easily expandable. \r\n\r\nWe at Springload seriously consider repurposing this package to provide us `DraftailOnlyRichTextField` and `DraftailOnlyRichTextBlock` that is going to utilize standard Draftail features from Wagtail 2, but keep the rich text data in database represented by draftails content state json object. So feature main control it's final end user html without overhead of converting into db html string and back. The same way how it works by using this package prior Wagtail 2."}}
{"actor":{"display_login":"mojeto"}}