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

Impossible to have nested routes and layouts that do not unmount? #23395

Closed
nolandg opened this issue Apr 23, 2020 · 2 comments
Closed

Impossible to have nested routes and layouts that do not unmount? #23395

nolandg opened this issue Apr 23, 2020 · 2 comments
Labels
stale? Issue that may be closed soon due to the original author not responding any more. type: question or discussion Issue discussing or asking a question about Gatsby

Comments

@nolandg
Copy link

nolandg commented Apr 23, 2020

I've read all of the below resources and more and from I can tell, Gatsby is incapable of handling nested layouts that do not unmount. You can make a single global layout that doesn't unmount by using the wrapRootElement method. You can make many nested layouts normally like any React structure. But you cannot have a nested layout component that doesn't unmount on route change. Is that correct?

I have a main left bar menu and then some sub section menus in the main content area. User navigates from /app/parent-menu-1/child-menu-1 to /app/parent-menu-1/child-menu-2. It is now impossible to do that transition without unmounting child menu layout. Correct?

Reach cannot do React Router nested routes? Any other options for animations between nested URLs?

https://www.gatsbyjs.org/tutorial/part-three/
https://www.gatsbyjs.org/docs/routing/
#6127

@nolandg nolandg added the type: question or discussion Issue discussing or asking a question about Gatsby label Apr 23, 2020
@github-actions
Copy link

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

@github-actions github-actions bot added the stale? Issue that may be closed soon due to the original author not responding any more. label May 13, 2020
@github-actions
Copy link

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community! 💪💜

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale? Issue that may be closed soon due to the original author not responding any more. type: question or discussion Issue discussing or asking a question about Gatsby
Projects
None yet
Development

No branches or pull requests

1 participant