-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Laravel Passport 13.x #1453
Comments
Thanks for your patience and work on this @hafezdivandari - as noted, I had an emergency at work which I'm sure you will appreciate, takes precedence over work I do in my free time. I'm available to start looking at this now though and had planned on doing so this evening. Thanks |
Just a quick update. I haven't forgotten about this @hafezdivandari and have started reviewing 1412. I'll aim to have another two PRs reviewed this week. Cheers! |
As with anything, it is just double checking the specs that is the slow part really. I put in well over a year to the device code grant. It went through numerous iterations and a release candidate with everything fully tested and still compliance issues slipped through :) Thank you for all your help with this though and I will be sure to shout should I need anything! |
Totally understandable, I tried to mention the related spec section on each PR (I'll recheck them all again), and added tests wherever required. |
Next on the list. I did take a look tonight but quite a few moving parts to it. Will get to it asap |
It's about time we released Laravel Passport 13.x, but we are being held back due to unmerged PRs in this repo after 5 months!
There are 4 bugs, that I've previously sent PRs to address them:
And also 4 more PRs which would be really appreciated if we can merge before major Passport release:
Originally posted by @hafezdivandari in laravel/passport#1748 (comment)
The text was updated successfully, but these errors were encountered: