Skip to content

Use callable classes for custom Monolog processors #10125

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 27, 2018

Conversation

jaikdean
Copy link

The built-in Monolog processors all use callable classes with an __invoke() method, whereas the Symfony documentation uses a processRecord() method. Using __invoke() provides consistency with the standard processors and also removes the need to specify the method name in the service configuration.

@javiereguiluz
Copy link
Member

@jaikdean I've just checked Monolog and you are totally right! Let's make this change because it's consistent and simplifies things a lot. Thanks for helping us improve Symfony Docs and congrats on your first contribution to this repository!

@javiereguiluz javiereguiluz merged commit 6f1a0f3 into symfony:2.8 Jul 27, 2018
javiereguiluz added a commit that referenced this pull request Jul 27, 2018
…dean)

This PR was merged into the 2.8 branch.

Discussion
----------

Use callable classes for custom Monolog processors

The built-in Monolog processors all use callable classes with an `__invoke()` method, whereas the Symfony documentation uses a `processRecord()` method. Using `__invoke()` provides consistency with the standard processors and also removes the need to specify the method name in the service configuration.

Commits
-------

6f1a0f3 Use callable classes for custom Monolog processors
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