-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Bug in named arguments since 5.4.17, not fixed by fix in 5.4.19 #49118
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
Comments
Can you please provide a small reproducing app? |
Here is an example app: https://github.com/nutama/symfony-named-arguments-issue Issue will trigger during the It will work when rolling back to symfony/dependecy-injection:5.4.17
|
Perfect thanks, I should have a fix tomorrow! |
…ositional and named ones (nicolas-grekas) This PR was merged into the 5.4 branch. Discussion ---------- [DependencyInjection] Fix order of arguments when mixing positional and named ones | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #49118 | License | MIT | Doc PR | - Commits ------- 45d614d [DependencyInjection] Fix order of arguments when mixing positional and named ones
Hi @nicolas-grekas thanks again for the fix! Could a tag be created as well (or is there a set policy for when that is done)? Would fix our latest builds from failing. |
It will be created eventually, but we don't push new releases for every bugfix we merge. Please use |
Symfony version(s) affected
5.4.17, 5.4.19
Description
The fix in named arguments in 5.4.17 triggered issues which 5.4.19 rectified. But seems to have not fixed all cases.
How to reproduce
Above service configuration will trigger:
Adding them both to
bind
or both toarguments
will work (but is undesired).Possible Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: