You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…nts (rpkamp)
This PR was squashed before being merged into the 5.2-dev branch.
Discussion
----------
[DependencyInjection] Resolve parameters in tag arguments
| Q | A
| ------------- | ---
| Branch? | master
| Bug fix? | no
| New feature? | yes
| Deprecations? | no
| Tickets | Fix#35337
| License | MIT
| Doc PR | None, yet, will follow if this is accepted
Arguably this could be a BC break if people are actively relying on parameters not being resolved in tag parameters, although I can't come up with a sensible use case for that scenario.
Commits
-------
3dba1fe [DependencyInjection] Resolve parameters in tag arguments
…g arguments" (rpkamp)
This PR was merged into the 5.2-dev branch.
Discussion
----------
Revert "[DependencyInjection] Resolve parameters in tag arguments"
| Q | A
| ------------- | ---
| Branch? | master
| Bug fix? | no
| New feature? | no
| Deprecations? | no
| Tickets | #35337
| License | MIT
| Doc PR | N/A
Revert of earlier PR, see discussion #37243
Commits
-------
9731451 Revert "[DependencyInjection] Resolve parameters in tag arguments"
Description
When using a
!tagged_locator
with anindex_by
value, we can not use parameters inside thoseindex_by
values.Example
parameters.yaml
services.yaml
Expected behaviour
I expect to be able to call the tagged_locator with the
bar
service (because%foo%
isbar
)Actual behaviour
The service locator throws an exception that the service
bar
does not exist, only the service%foo%
exists.The text was updated successfully, but these errors were encountered: