-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
[5.x] fix: duplicate route names #313
Conversation
Personal Note: requires tests to ensure caching isn't broken |
any progress on this? |
I just ran into this error. Glad the solution already exists. Will wait for the next release. Thanks for the package! |
@Supernova3339 nope. I've had a pretty bad flu/cold for the last week or so and still recovering. Will carve out some time for it this week, but I have no set date for release. When it's out, you will be the first to know 👍 |
Awesome! Thanks, Joel!
…On Fri, Nov 17, 2023, 3:28 PM Joel Butcher ***@***.***> wrote:
Merged #313 <#313> into
5.x.
—
Reply to this email directly, view it on GitHub
<#313 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APESZJWBIT5BOHMBSUS6ZX3YE7JG5AVCNFSM6AAAAAA7AIUBIOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQHE4TSMRYGMZTIOA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Uses
Route::match(…)
to resolve the OAuth callback for both GET and POST HTTP verbs in order to cache the route for both methods with the same name.Addresses issues identified in #288