mirror of
https://github.com/Seldaek/monolog.git
synced 2026-04-26 08:05:53 +03:00
[GH-ISSUE #436] choose backtrace level in IntrospectionProcessor #148
Labels
No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/monolog#148
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pactole on GitHub (Oct 14, 2014).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/436
Hi Jordi,
We've override Monolog in our project
This override makes the IntrospectionProcessor not working because our current back_trace level is 3 instead of 2 in your code.
I've been forced to fork your IntrospectionProcessor Class because the properties you declare are private ($level, $skipClassesPartials).
The Idea is to set a backtrace_level property to execute array_shift($trace) n times
I may be wrong in the use of the proscessors to get the proper line, file, class and function.
In the case I'm not wrong... could the properties declared in IntrospectionProcessor be protected?
Do you need a pull request for that?
Best regards, and keep on the good work!
Jacques
@Seldaek commented on GitHub (Oct 15, 2014):
You can probably just fix it by tweaking the $skipClassesPartials argument when you construct it. For example if your class extending
Monolog\Loggeris calledFoo\Barjust pass inarray('Foo\\Bar','Monolog\\')so it ignores your class from the backtrace as well.@pactole commented on GitHub (Oct 15, 2014):
Thanks for the reply!
I'll try that and leave a comment.
Have a nice day
Jacques
@pactole commented on GitHub (Oct 17, 2014):
I had to make a lot of refactorisation as the original implementation didn't fit Monolog standards.
And It works :).
@Seldaek commented on GitHub (Oct 17, 2014):
OK cool, closing this then.