it'd be nice to store computed values in something like getState().cashay.computed.teamSubs.
This is something that reselect doesn't do, but since cashay is used for bigger apps, it starts to make sense.
The problem is deciding what to do for the memoization triggers. If they're primitives, it's easy. If they're objects, it's still pretty easy since we just do a reference check. But if it's a function, it gets ugly because we can't store functions in the redux store (if we want to stringify it).
So, we can either disallow support for functions, or we can store the inputs outside the redux store & just save the result.
mattkrick
commented
8 years ago
it'd be nice to store computed values in something like
getState().cashay.computed.teamSubs. This is something that reselect doesn't do, but since cashay is used for bigger apps, it starts to make sense.The problem is deciding what to do for the memoization triggers. If they're primitives, it's easy. If they're objects, it's still pretty easy since we just do a reference check. But if it's a function, it gets ugly because we can't store functions in the redux store (if we want to stringify it).
So, we can either disallow support for functions, or we can store the inputs outside the redux store & just save the result.