4 ms·

Thanks, this is important, but definitely out of scope of my tiny component. Stoppable and revertable transitions - does it really need to be a same component

Thanks, this is important, but definitely out of scope of my tiny component. Stoppable and revertable transitions - does it really need to be a same component (A:child -> B:parent -> A:child)? Wouldn't adding another component instance with a same props suffice (A:child -> B:parent -> C:child)? Then I guess it could be hacked with transitions, but if you require (A -> B -> A), then it seems to me like something that would need some support from higher layers (router?)...

chenglou 12y ago
I don't think it has to do with router; just pure, simple state (router is just another part of a component state anyways). For your example, I think it should support both. You can distinguish an A from another A through a different key or something. If it's the same key, you'd want it to "unmount back".
deleted 12y ago
[deleted]