Replies: 2 comments
-
You should do:
Which entails a page file as OR
Which entails a page file as The difference between Hard (known?) pages can be done via This is all in the docs ;-) x |
Beta Was this translation helpful? Give feedback.
-
This to me feels like an inconsistency in the API hence the bug report. For example, when I want a I would expect next client router to automatically know about catch-all page routes so that if I attempt to call |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Bug report
Describe the bug
When pushing a route that is handled by a catch-all page, I expect the routing to happen client-side. Instead, the entire page reloads and server-side routing is used.
For example, suppose I have defined the following page:
And suppose I have the following links defined somewhere:
When I click on
Page 1
, the page reloads as the routing happens server-side which is not ideal.When I click on
Page 2
, the routing happens client-side which is ideal.To Reproduce
git clone https://github.com/keyworks/next-catch-all-client-routing-issue.git
yarn dev
and visitlocalhost:3000
Page 1
linkExpected behavior
Page should not reload, but instead page transition should happen client side.
Screenshots
n/a
System information
Additional context
n/a
Beta Was this translation helpful? Give feedback.
All reactions