Closed bringking closed 4 years ago
@fridays any chance on getting this merged? Any way that we can help?
Seconded, this is required for us too.
@fridays friendly bump, would love to get these fixes merged. Any way we can help or do you need maintainers on this project?
@fridays bump
Wouldn't you write this in to pattern instead?
@fridays are you maintaining this anymore? If not, please let us know so we can fork and maintain ourselves. Or add a contributor 🙏
@bringking you probably wanna ping @elliottsj here, see: https://github.com/fridays/next-routes/issues/244
@Timer or @elliottsj could this PR be merged and released, as it fixes an issue we are having currently. Nextjs dynamic routing doesnt cover all the cases we need for our site, so we are using next-routes until it does but we are seeing this bug happening at the moment and is an easy fix. Thank you!
We are running into an issue adding query strings to Next routes. For example, when viewing a "reviews" page like so -
/someurl/:slug/reviews
we need to paginate with a query string like -/someurl/my-slug/reviews?page=1
This works fine if you push a shallow route with
Link
however, on SSR reloads, only the named param segments are added to theprops.url.query
for the page. This fixes this by mergingparams
and thequery
with named params taking precedence