Skip to content

Conversation

@LaurentQ56
Copy link
Contributor

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 is lock.xxx.factory. xxx being 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.

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.
@carsonbot carsonbot added this to the 6.4 milestone Oct 23, 2025
@carsonbot carsonbot changed the title fix(documentation): reorder service id on target attribute fix(documentation): reorder service id on target attribute Oct 23, 2025
@carsonbot carsonbot changed the title fix(documentation): reorder service id on target attribute [Lock] fix(documentation): reorder service id on target attribute Oct 27, 2025
Copy link
Member

@javiereguiluz javiereguiluz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@javiereguiluz javiereguiluz merged commit f44e21d into symfony:6.4 Oct 27, 2025
3 checks passed
@LaurentQ56
Copy link
Contributor Author

Looking at the code:

https://github.com/symfony/symfony/blob/a8aacb860335ac1e3bf75931ed43da5bbc483580/src/Symfony/Bundle/FrameworkBundle/DependencyInjection/FrameworkExtension.php#L2096

Shouldn't both formats work? 🤔

With Symfony 6.4, when I used it in #[Traget] attribute, it throws a not found exception. 😕

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants