Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Edge case request - ability to opt out of urlencoding
See original GitHub issuehttps://www.redfin.com/city/30818/TX/Austin/filter/min-price=100k,max-price=325k
I am building something that updates the state of the url based on a set of filters, Redfin’s site is almost an exact match to my intended effect. The last ‘route’ portion is the /filter/ and everything after that are a series of filters that we are parsing and can be in any combination or order
Do you have a suggestion for how I can achieve this with next-routes? We are already using it but the problem is everything after filter/ gets urlencoded which produces some very ugly urls.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+1
Ah you’re right. I didn’t check so carefully and assumed it was using the Router.push / Router.replace of nextjs which I found was using the url package.