{"action":"created","issue":{"url":"https://api.github.com/repos/ckeditor/ckeditor5-ui/issues/73","repository_url":"https://api.github.com/repos/ckeditor/ckeditor5-ui","labels_url":"https://api.github.com/repos/ckeditor/ckeditor5-ui/issues/73/labels{/name}","comments_url":"https://api.github.com/repos/ckeditor/ckeditor5-ui/issues/73/comments","events_url":"https://api.github.com/repos/ckeditor/ckeditor5-ui/issues/73/events","html_url":"https://github.com/ckeditor/ckeditor5-ui/issues/73","id":176384790,"number":73,"title":"Why do we need a view models?","user":{"login":"Reinmar","id":156149,"avatar_url":"https://avatars.githubusercontent.com/u/156149?v=3","gravatar_id":"","url":"https://api.github.com/users/Reinmar","html_url":"https://github.com/Reinmar","followers_url":"https://api.github.com/users/Reinmar/followers","following_url":"https://api.github.com/users/Reinmar/following{/other_user}","gists_url":"https://api.github.com/users/Reinmar/gists{/gist_id}","starred_url":"https://api.github.com/users/Reinmar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Reinmar/subscriptions","organizations_url":"https://api.github.com/users/Reinmar/orgs","repos_url":"https://api.github.com/users/Reinmar/repos","events_url":"https://api.github.com/users/Reinmar/events{/privacy}","received_events_url":"https://api.github.com/users/Reinmar/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ckeditor/ckeditor5-ui/labels/status:discussion","name":"status:discussion","color":"e6e6e6"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-09-12T14:08:37Z","updated_at":"2016-09-12T15:11:19Z","closed_at":null,"body":"OK, I hate to say that, but I don't remember or I don't know the answer. Either way, it sounds like we overcomplicated this thing...\r\n\r\nSo, currently we say – the view model (created automatically by each view and used by controllers to push data into the views and get the feedback) is the view's interface. It's how the world communicates with the view.\r\n\r\nThat's even fine, but:\r\n\r\n* It looks like we haven't followed that rule: https://github.com/ckeditor/ckeditor5-ui-default/issues/70 and I also don't know how to make richer methods (like those `attachTo()` – I guess its params should be put in the view model...).\r\n* If the view model is the views public API, then what's left in the view itself? What does its public API represent? We've got there methods like `init()` and `destroy()` plus couple of other things, but still... why moving the rest outside?"},"comment":{"url":"https://api.github.com/repos/ckeditor/ckeditor5-ui/issues/comments/246379734","html_url":"https://github.com/ckeditor/ckeditor5-ui/issues/73#issuecomment-246379734","issue_url":"https://api.github.com/repos/ckeditor/ckeditor5-ui/issues/73","id":246379734,"user":{"login":"pjasiun","id":1166967,"avatar_url":"https://avatars.githubusercontent.com/u/1166967?v=3","gravatar_id":"","url":"https://api.github.com/users/pjasiun","html_url":"https://github.com/pjasiun","followers_url":"https://api.github.com/users/pjasiun/followers","following_url":"https://api.github.com/users/pjasiun/following{/other_user}","gists_url":"https://api.github.com/users/pjasiun/gists{/gist_id}","starred_url":"https://api.github.com/users/pjasiun/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pjasiun/subscriptions","organizations_url":"https://api.github.com/users/pjasiun/orgs","repos_url":"https://api.github.com/users/pjasiun/repos","events_url":"https://api.github.com/users/pjasiun/events{/privacy}","received_events_url":"https://api.github.com/users/pjasiun/received_events","type":"User","site_admin":false},"created_at":"2016-09-12T15:11:19Z","updated_at":"2016-09-12T15:11:19Z","body":"It looks like the most classic MVC approach for me, what is nice and easy to understand."}}
{"actor":{"display_login":"pjasiun"}}