-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[HttpClient] Allow to pass user/pw as an array #30556
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
Conversation
This one needs to be rebased :) |
Thank you @dunglas. |
This PR was merged into the 4.3-dev branch. Discussion ---------- [HttpClient] Allow to pass user/pw as an array | Q | A | ------------- | --- | Branch? | master <!-- see below --> | Bug fix? | no | New feature? | yes<!-- don't forget to update src/**/CHANGELOG.md files --> | BC breaks? | no <!-- see https://symfony.com/bc --> | Deprecations? | no <!-- don't forget to update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tests pass? | yes <!-- please add some, will be required by reviewers --> | Fixed tickets | n/a <!-- #-prefixed issue number(s), if any --> | License | MIT | Doc PR | n/a Makes the API a bit more "PHPish". Commits ------- 8d5096a [HttpClient] Allow to pass user/pw as an array
Do we really want to allow two different ways of doing the same thing? Maybe allowing only the use of arrays instead of strings could be enough? |
I wouldn't mind having only the array way. Makes sense to me. WDYT @dunglas @nicolas-grekas? |
Being allowed to pass a string doesn't hurt IMO (as it's a standard), but if we have to choose only one I'll go for the array way too. |
The string is the only thing that the standard describes. The array is only sugar, and leaks actually (you can't use a I'm for keeping the string of there should be only one. |
Makes the API a bit more "PHPish".