Skip to content

[DependencyInjection] Use Notifier transport_factory services (without fqcn) #53433

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

Closed
wants to merge 1 commit into from

Conversation

smnandre
Copy link
Member

@smnandre smnandre commented Jan 5, 2024

Q A
Branch? 7.1
Bug fix? no
New feature? no
Deprecations? no
Issues Fix #
License MIT

Follows #53418 (cc @nicolas-grekas )

@carsonbot carsonbot added this to the 7.1 milestone Jan 5, 2024
@carsonbot carsonbot changed the title [DI] Use Notifier transport_factory services (without fqcn) [DependencyInjection] Use Notifier transport_factory services (without fqcn) Jan 5, 2024
@OskarStark
Copy link
Contributor

Discoverability for new bridges is much better with the FQCN

@smnandre
Copy link
Member Author

smnandre commented Jan 6, 2024

It follows the previous PR/discussion, where we realized some of those FQCN were missconfigured since ... a bit of time :)

Maybe instead we could only use the FQCN then instead of the service id ?

The main goal was to avoid any situation were we use a map classA => service in a file and classB => service in another, without ensuring classA = classB.

@nicolas-grekas
Copy link
Member

Discoverability for new bridges is much better with the FQCN

I think that's a nice argument. Mistakes can happen so while this prevents some kind of mistakes, in might open others.
Closing therefor, thanks for proposing.

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.

4 participants