You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions
Description
Since the router, like @reach/router, doesn't seem to support optional parameters, my use-case is to simulate an optional parameter in an editor that should not get remounted:
This repository is for issues related to Gatsby. In client-side only routes of Gatsby you can use any router you want, you don't need to use reach-router. We only use a forked version of it for our own SPA navigations.
Preliminary Checks
Description
Since the router, like @reach/router, doesn't seem to support optional parameters, my use-case is to simulate an optional parameter in an editor that should not get remounted:
Once
someId
is processed, wenavigate('/')
.But the issue is that the editor gets remounted and loses state.
It seems that this was an issue introduced between
@reach/[email protected]
and1.3.4
Another useful description and a repro is here (gh issue link).
Reproduction Link
https://github.com/gustafc/reach-remounts
Steps to Reproduce
See the instructions in the repro repo.
Expected Result
The above routing config should not unmount any part of
<App />
Actual Result
The above routing config unmounts and remounts all of
<App />
Environment
Config Flags
No response
The text was updated successfully, but these errors were encountered: