-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Suggestion: Ability to pass objects into Mage log for custom log writers. #89
Comments
Thank you for the suggestion. |
magento-engcom-team
added a commit
that referenced
this issue
Mar 15, 2018
- Merge Pull Request magento-engcom/php-7.2-support#89 from magento-engcom/php-7.2-support:update-zend-feed - Merged commits: 1. b73d1c8
magento-engcom-team
pushed a commit
that referenced
this issue
Mar 15, 2018
ghost
mentioned this issue
May 3, 2018
magento-engcom-team
pushed a commit
that referenced
this issue
Jun 21, 2018
magento-engcom-team
pushed a commit
that referenced
this issue
Jun 21, 2018
magento-engcom-team
pushed a commit
that referenced
this issue
Jun 21, 2018
magento-engcom-team
pushed a commit
that referenced
this issue
Jun 21, 2018
magento-engcom-team
pushed a commit
that referenced
this issue
Jun 21, 2018
…-Category [architects] MAGETWO-92773: [GraphQL] Products cannot be fetched in parent/anchor category #89
magento-engcom-team
pushed a commit
that referenced
this issue
Oct 12, 2019
Rebasing MC-19451 with the changes of MC-19450-elastic branch
5 tasks
5 tasks
magento-devops-reposync-svc
pushed a commit
that referenced
this issue
Mar 15, 2023
…stomer groups on single scenarios (#89)
5 tasks
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating own log writers it would be really useful to be able to pass objects into mage log, this extra useful when not using a file based log.
the problem is that a check is made to see if the message is a object and if so it does a print_r to make it to string but at the same destroying the possibility to use it later.
You can get around it right now by temporarily store the log data and catch in the log writer but it isn't as nice that it could be.
The text was updated successfully, but these errors were encountered: