{"action":"created","issue":{"url":"https://api.github.com/repos/moreartyjs/moreartyjs/issues/81","labels_url":"https://api.github.com/repos/moreartyjs/moreartyjs/issues/81/labels{/name}","comments_url":"https://api.github.com/repos/moreartyjs/moreartyjs/issues/81/comments","events_url":"https://api.github.com/repos/moreartyjs/moreartyjs/issues/81/events","html_url":"https://github.com/moreartyjs/moreartyjs/issues/81","id":73737852,"number":81,"title":"Working with history","user":{"login":"Theadd","id":78041,"avatar_url":"https://avatars.githubusercontent.com/u/78041?v=3","gravatar_id":"","url":"https://api.github.com/users/Theadd","html_url":"https://github.com/Theadd","followers_url":"https://api.github.com/users/Theadd/followers","following_url":"https://api.github.com/users/Theadd/following{/other_user}","gists_url":"https://api.github.com/users/Theadd/gists{/gist_id}","starred_url":"https://api.github.com/users/Theadd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Theadd/subscriptions","organizations_url":"https://api.github.com/users/Theadd/orgs","repos_url":"https://api.github.com/users/Theadd/repos","events_url":"https://api.github.com/users/Theadd/events{/privacy}","received_events_url":"https://api.github.com/users/Theadd/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-05-06T21:11:09Z","updated_at":"2015-05-07T09:47:38Z","closed_at":"2015-05-07T09:47:38Z","body":"You're really doing a great job! :100:\r\nWorking with the tree of state bindings was... ok, but by just writing a ~couple more lines to work with the history module was awesome!\r\n\r\nCould it be possible to _stack|group|merge|remove|*_ some points of state in history so when calling undo/redo it treats those states as a single one instead of iterating each one for every history call?\r\n\r\nMaybe by disabling/enabling the history before/after a .set() or .update? I've tried with `{ notify: false }` but I didn't notice anything different:\r\n```jsx\r\nthis.getDefaultBinding().atomically().\r\n  set(\"meshMap\", Imm.List(collection._items)).\r\n  commit({ notify: false });\r\nthis.forceUpdate();\r\n```\r\nMaybe because `this.getDefaultBinding()` was a sub-binding of the one initialized with history instead of the history one?"},"comment":{"url":"https://api.github.com/repos/moreartyjs/moreartyjs/issues/comments/99797089","html_url":"https://github.com/moreartyjs/moreartyjs/issues/81#issuecomment-99797089","issue_url":"https://api.github.com/repos/moreartyjs/moreartyjs/issues/81","id":99797089,"user":{"login":"Theadd","id":78041,"avatar_url":"https://avatars.githubusercontent.com/u/78041?v=3","gravatar_id":"","url":"https://api.github.com/users/Theadd","html_url":"https://github.com/Theadd","followers_url":"https://api.github.com/users/Theadd/followers","following_url":"https://api.github.com/users/Theadd/following{/other_user}","gists_url":"https://api.github.com/users/Theadd/gists{/gist_id}","starred_url":"https://api.github.com/users/Theadd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Theadd/subscriptions","organizations_url":"https://api.github.com/users/Theadd/orgs","repos_url":"https://api.github.com/users/Theadd/repos","events_url":"https://api.github.com/users/Theadd/events{/privacy}","received_events_url":"https://api.github.com/users/Theadd/received_events","type":"User","site_admin":false},"created_at":"2015-05-07T09:47:38Z","updated_at":"2015-05-07T09:47:38Z","body":"well, I've used forceUpdate() + observedProps (passing the transaction context as prop) but since I don't commit that transaction, the default binding in nested components does not reflect those changes so nested components doesn't even need to update.\r\n\r\nI might have to refactor that part a little bit to be able to update the binding within the same component."}}