-
-
Notifications
You must be signed in to change notification settings - Fork 893
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
feat(swagger-ui): persist authorization #6877
feat(swagger-ui): persist authorization #6877
Conversation
I second this change. It's much better to have the ability to persist authorization rather than having to type in the PKCE client ID each time. |
can you target the 4.1 or main branch? |
only 4.1 version (branch) is OK for me ❤️ |
@soyuka Do I need to do anything else? |
I changed the target branch to 4.1 but this needs a rebase, also it looks like test failures are related, feel free to ping me on slack if you've trouble running tests. |
@soyuka I fixed the merge conflicts and tests (my unit tests are also running locally), but some Laravel tests are still crashing. Can you please take a look? Thank you. |
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 can add these myself feel free to comment if you've a question. I'll probably release that tomorrow in a beta version.
src/Symfony/Bundle/DependencyInjection/ApiPlatformExtension.php
Outdated
Show resolved
Hide resolved
@soyuka thanks... perfect |
[FTR] add Swagger UI config directive: persistAuthorization