-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optional catch all routes [[...category]] route ? #12
Comments
Hi Truong! Glad you like it :) And thanks for submitting this issue. I didn't think about that use case, no. I will have a look at supporting it very soon. /Christian |
@revskill10 after a bit of thinking, I feel like I found a decent solution for this use case :) |
I've released the changes as I didn't want to keep the PR open too long. If this doesn't solve your issue, let me know. And I'll have another look at it :) |
@ckastbjerg Huge thanks. I'll try out and post issues if i've got any ! |
For further investigation, if you have a look at i18n routing, it would be awesome 👯♂️ |
Hi, thanks for great library.
I have one issue about wildcard route, like
/store/[store]/[[...category]]
, i see it generates as route/store/[store]/[[
only.Could you please check this use case ?
The text was updated successfully, but these errors were encountered: