Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
[Lock] fix(documentation): reorder service id on target attribute#21531
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
When I use the name with suffix `.lock.factory`, the service was not found.After a `debug:container LockFatory`, I see the service ID is `lock.xxx.factory`. `xxx` being the named service wanted.
javiereguiluz left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
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.
Looking at the code:
Shouldn't both formats work? 🤔
f44e21d intosymfony:6.4Uh oh!
There was an error while loading.Please reload this page.
LaurentQ56 commentedOct 27, 2025
With Symfony 6.4, when I used it in |
When I use the name of named configuration with suffix
.lock.factory, the service was not found.After a
debug:container LockFatory, I see the service ID islock.xxx.factory.xxxbeing the named configured lock wanted.My version is 6.4, but I haven't checked whether this error is still present in the current version.