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
When there are only two simple parameters, routing fails... #162
Conversation
…tain routes, i.e. "/personnel/{:personnel_id}/position/{:position_id}/action/create".
…ior, provided for clarity.
BTW, I rebased to the current (as of today) master after making that pull request, which of course changed my commits. If github doesn't know what to do with it, I'll reopen my pull request. |
This is related to issue #157 #154 more tests cases here mehlah@33089d4 |
Is there a regex master who can explain why this happens and what's exactly going on ? :-) |
@ifunk: sure, I understand the role played by the |
Since you essentially used the code from this pull request in your own commit verbatim, wouldn't it have been easier just to accept the pull request? Or am I missing some contributor politics here...? |
Sorry, it was mostly laziness. The fix itself was the same, but I ended up completely rewriting the test to be exhaustive in terms of the cases it covers. Anyway, I couldn't remember the series of commands to amend someone else's work but still maintain attribution. |
See |
Heh, nice. Thanks. |
I added a test to
lithium/tests/cases/net/http/RouteTest.php
to reflect a route that we were attempting to use in our project that was failing to route. My guess is that the regex inRoute::compile():366
is incorrectly seeing the second pattern as the regex part of the first pattern. I made that capture pattern lazy and got greens. Please review. Thanks,David @ OrlandoPHP.org