{"action":"opened","issue":{"url":"https://api.github.com/repos/pemrouz/ripple/issues/14","labels_url":"https://api.github.com/repos/pemrouz/ripple/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/pemrouz/ripple/issues/14/comments","events_url":"https://api.github.com/repos/pemrouz/ripple/issues/14/events","html_url":"https://github.com/pemrouz/ripple/issues/14","id":57248770,"number":14,"title":"Immutable Data","user":{"login":"pemrouz","id":2184177,"avatar_url":"https://avatars.githubusercontent.com/u/2184177?v=3","gravatar_id":"","url":"https://api.github.com/users/pemrouz","html_url":"https://github.com/pemrouz","followers_url":"https://api.github.com/users/pemrouz/followers","following_url":"https://api.github.com/users/pemrouz/following{/other_user}","gists_url":"https://api.github.com/users/pemrouz/gists{/gist_id}","starred_url":"https://api.github.com/users/pemrouz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pemrouz/subscriptions","organizations_url":"https://api.github.com/users/pemrouz/orgs","repos_url":"https://api.github.com/users/pemrouz/repos","events_url":"https://api.github.com/users/pemrouz/events{/privacy}","received_events_url":"https://api.github.com/users/pemrouz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-10T22:36:51Z","updated_at":"2015-02-10T22:36:51Z","closed_at":null,"body":"TODO: \r\n\r\n* [ ] Make resource bodies persistent data structures with mori.\r\n* [ ] Freeze/thaw on change/retrieval to let consumers keep using vanilla types.\r\n* [ ] Replace resource body property with array of versions (with default upper limit)\r\n* [ ] After versioning resources, version entire application state (referencing resource versions)\r\n* [ ] Implement a time travel debugger!\r\n\r\n@mamapitufo @sammyt @mstade @gabrielmontagne @jkimbo - have you guys tried any of the immutable libs (mori, immutable-js, ancient oak, hamt, etc) or rolling your own? Do you have any thoughts/preferences/advice on which to use? \r\n\r\nThe only alternative to this I can think of is to store changes as diffs. The only issue with that is computing the state at a point in time is relatively more complicated, but we could cache the latest."}}