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 ticket is made in continuation to our conversation here: #588 (comment)
As mentioned here, just like the client side navigation logic will try to add a slash if /example-route isn't found but /example-route/ is, I'd expect the same behaviour from the router when dealing with routes having query parameters.
The simplest reproducer of this issue is:
Create a file named Index.kt inside your_package.pages.results package
Create a composable annotated with @Page
Once done, try to run this URL from your browser:
http://localhost:8080/results/?search_query=test
The router should be able to find and display your page
Then try to run this from your browser:
http://localhost:8080/results?search_query=test
Observe that the router is not able to find this URL.
The text was updated successfully, but these errors were encountered:
This ticket is made in continuation to our conversation here: #588 (comment)
As mentioned here, just like the client side navigation logic will try to add a slash if
/example-route
isn't found but/example-route/
is, I'd expect the same behaviour from the router when dealing with routes havingquery parameters
.The simplest reproducer of this issue is:
Index.kt
insideyour_package.pages.results
package@Page
The text was updated successfully, but these errors were encountered: