-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Fix routes options to be recognizable via used HTTP request method #3751
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this. I agree with @samsonasik's changes, also... I know getRoutes()
has an unspecified variable type on $verb
but other things will break if it is not string|null
so I think we should go ahead and update the function declaration to be consistent.
Co-authored-by: Abdul Malik Ikhsan <samsonasik@gmail.com> Co-authored-by: John Paul E. Balandan, CPA <51850998+paulbalandan@users.noreply.github.com>
Thanks for your code suggestions guys. |
👍 i was writing a bug report just at this moment and saw the merge while digging for the buggy code 🎆 |
Description
This PR fixes routes options to be recognizable via used HTTP request method. Right now routes options are shared - one instance per route. It leads to problems like: wrong named route name returned or firing incorrect filter.
I don't think this will introduce any BC, rather will fix buggy behavior, but if anyone notices the problem please let me know.
Fixes #3700
Fixes #3733
Checklist: