{"action":"closed","issue":{"url":"https://api.github.com/repos/rackt/redux/issues/800","labels_url":"https://api.github.com/repos/rackt/redux/issues/800/labels{/name}","comments_url":"https://api.github.com/repos/rackt/redux/issues/800/comments","events_url":"https://api.github.com/repos/rackt/redux/issues/800/events","html_url":"https://github.com/rackt/redux/issues/800","id":108279069,"number":800,"title":"Computed derived data access from multiple components","user":{"login":"tnrich","id":2730609,"avatar_url":"https://avatars.githubusercontent.com/u/2730609?v=3","gravatar_id":"","url":"https://api.github.com/users/tnrich","html_url":"https://github.com/tnrich","followers_url":"https://api.github.com/users/tnrich/followers","following_url":"https://api.github.com/users/tnrich/following{/other_user}","gists_url":"https://api.github.com/users/tnrich/gists{/gist_id}","starred_url":"https://api.github.com/users/tnrich/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tnrich/subscriptions","organizations_url":"https://api.github.com/users/tnrich/orgs","repos_url":"https://api.github.com/users/tnrich/repos","events_url":"https://api.github.com/users/tnrich/events{/privacy}","received_events_url":"https://api.github.com/users/tnrich/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-09-25T07:48:18Z","updated_at":"2015-09-25T08:48:03Z","closed_at":"2015-09-25T08:48:03Z","body":"Hey there, I'm coming to this project from baobab, and one of the features I like best about baobab is the ability to compute derived data from the state tree and store it in the state tree.\r\n\r\nHere's an example of what that would look like in baobab: \r\n```javascript\r\n{\r\n\tfoo: 'bar',\r\n\tbaz: 'yip'\r\n\tderivedNode: deriveData(['foo'], ['baz'], function(foo, baz) {\r\n\t\treturn foo + baz\r\n\t})\r\n}\r\n```\r\n\r\nIn my components I could then access 'derivedNode' like any other data within the tree. This would work well if I needed that data across multiple top level components.\r\n\r\nI read the docs section about the memoized selector function, which seems like a nice solution for generating derived data, but I was wondering what to do if you needed the derived data across multple \"smart\" components. Do they each have to implement the same selector function on the connect call? \r\n\r\nJust started checking out this library today so I hope my question makes sense.\r\n\r\nWhile I'm here... \r\nAnother quick question I have, it seems like for every reducer added to the store, another set of action type strings need to be checked against. Does this method ever encounter issues with scale?  Once many actions are being fired, it seems like it might be time consuming to compute all those switch statements. Has this ever been an issue for anyone?\r\n\r\nThanks very much,\r\nThomas"}}