Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any plans to support transitions of deeply nested components? #23

Closed
bdwain opened this issue Mar 20, 2017 · 3 comments
Closed

Any plans to support transitions of deeply nested components? #23

bdwain opened this issue Mar 20, 2017 · 3 comments

Comments

@bdwain
Copy link

bdwain commented Mar 20, 2017

It's currently difficult to do animations on unmount for deeply nested components if their parents are also unmounted because the transition group does not run componentWillLeave on them. Is there any plan to support this type of behavior (maybe using the context api?). I know it would greatly increase the complexity, but I'm just curious since it's a common issue I've seen people run into and current solutions I've seen involve making many unrelated pieces of the app aware of this transition.

@jquense
Copy link
Collaborator

jquense commented Mar 20, 2017

We don't have any plans for that specifically since would add a lot of complexity. We do however, hope to get to a point where there are more exposed hooks that should make it easier to implement such things yourself (in ways that make sense for your specific use cases)

@bdwain
Copy link
Author

bdwain commented Mar 20, 2017

cool. Thanks for the info. Is there anywhere I can see some examples of hooks you're planning to expose? I know nothing is finalized or anything, just trying to get a rough idea of the current direction.

@jquense
Copy link
Collaborator

jquense commented Apr 26, 2017

#24

@jquense jquense closed this as completed Apr 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants