-
Notifications
You must be signed in to change notification settings - Fork 11
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
wildcard issue in group router #19
Comments
link to line throwing code: Line 276 in b6e8fa9
|
I'll try to fix it during the weekend. I think the original intension of the Golang implementation is that, there should be only one route for any path. With that guarantee, it is possible to use goroutine to do an optimization on the route search. Anyway, this is not relevant in Node.js and should be fixed. |
@steambap dope for responding! i was just hacking my way through the source code ;) if you have an idea of what your going to do fix it, send it my way and hopefully we can share the burden. the information you've provided is helpful and clarifies why the error is there. |
Hi @noahehall , if you know how Golang works, you can just copy everything, including the tests, from here: |
I know golang about as good as I know swahili. I reviewed julienschmidt/httprouter#329 and it doesnt quite solve this issue, however would still be a net benefit. the issue fixed on httprouter is specific to routes with variable path segments, here we're concerned with catchalls [update] i’ll tackle it and submit a PR. |
unable to specify catchall route handler if a named route exist at the same level
issue:
purpose:
good/good/badname
problem:
good/good/goodname
here is a link to the actual code
here is a link to the handler definition
The text was updated successfully, but these errors were encountered: