8000 Mention how to inject a specific Monolog service by javiereguiluz · Pull Request #10049 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

Mention how to inject a specific Monolog service #10049

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

Merged
merged 1 commit into from
Jul 13, 2018

Conversation

javiereguiluz
Copy link
Member

This replaces #9849 and links to the explanation about how to wire specific services in the container.

@javiereguiluz javiereguiluz added this to the 3.4 milestone Jul 12, 2018
@javiereguiluz javiereguiluz merged commit 391d3e0 into symfony:3.4 Jul 13, 2018
javiereguiluz added a commit that referenced this pull request Jul 13, 2018
…eguiluz)

This PR was merged into the 3.4 branch.

Discussion
----------

Mention how to inject a specific Monolog service

This replaces #9849 and links to the explanation about how to wire specific services in the container.

Commits
-------

391d3e0 Mention how to inject a specific Monolog service
Symfony automatically registers one service per channel (in this example, the
channel ``foo`` creates a service called ``monolog.logger.foo``). In order to
inject this service into others, you must update the service configuration to
:ref:`choose the specific service to inject <services-wire-specific-service>`.
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't we rather link to the monolog.logger tag (https://symfony.com/doc/2.8/reference/dic_tags.html#dic-tags-monolog)?

6E24
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
0