[ben_jones]

Going to digress a bit but I'm working on a project in Vue and while at first it seemed like a literal breath of fresh air I came to the awful conclusion that no matter what SPA framework/library you're using, if it's javascript, you gonna be using webpack + a medium size build pipeline for es2015, jade, scss, bundling, file watching, hot-reload etc. The arguments for small libraries aren't as strong anymore because the advantages of the larger ones have enough cost/benefit that you're going to be pulling them in EVENTUALLY so might as well do it from the beginning.

[beaconstudios]

You don't happen to know how to get vuex working idiomatically with deeply nested data do you? I can work with it but only if I start passing around object references, which seems like a terrible idea.

[ben_jones]

No clue, haven't used vuex yet :/ .

[beaconstudios]

ah ok, no worries - I think it's similar to Redux largely, which unfortunately includes being severely incompatible with nested state values.

[girvo]

In redux I use functional lenses to create composoable getter/setter functions to handle deeply nested data safely. I do that even without redux, but it is very useful there. Take a look at the lens functions in Ramda, or safety-lens

[beaconstudios]

I'd never thought to use lenses for this. Thanks for the advice, that actually really helps!