Isolation scope name problems about cycle-onionify HOT 7 CLOSED

I think problem 1 can be solved with something like this: #3
It also depends if Child and AnotherChild just read state but don't write it. If that's the case, then state$ can be passed instead of sources.onion.

Problem 2:
It depends, if it's read-only state, we can do like I suggested above. Otherwise, we could consider supporting an API like isolate(Child, 'some.nested.child')

from cycle-onionify.

'some.nested.child' it is still imperfect solution, as object property itself may contain dot.

I like that onionify tries to unify ideas for managing state, though currently I prefer more transparent and custom solution, something that I described in recent gist: https://gist.github.com/whitecolor/0f015856a335ca418e22d4bba4d97d68

from cycle-onionify.

as object property itself may contain dot

I've never seen a single case of this. :)

from cycle-onionify.

What about obj['some.dots']?

from cycle-onionify.

I've also seen arrays of strings/numbers used to denote a nested path, as in isolate(Child, ['some', 'nested', 'child']). It's a little noisier than a dot-delimited string but it works if you're really worried about having dots in property names.

from cycle-onionify.

The lenses proposal in #11 would solve this issue entirely.

from cycle-onionify.

Solved by issue #11

from cycle-onionify.