starred/monolog
1
0
Fork 0
mirror of https://github.com/Seldaek/monolog.git synced 2026-04-26 08:05:53 +03:00
Code Issues 31 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #1728] Why does BrowserConsoleHandler always use console.log? #724

New issue
Closed
opened 2026-03-04 02:17:25 +03:00 by kerem · 2 comments
kerem commented 2026-03-04 02:17:25 +03:00
Owner
Copy link

Originally created by @pafernandez-oesia on GitHub (Jul 8, 2022).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/1728

Hi!

I was just wondering if there is any reason to use console.log method for all log levels, instead of also using debug, info, warn and error methods depending on the log level. This makes filtering output easier in the browser console and clearly highlights error level messages.

The following image shows an example output from Laravel using Monolog and a custom implementation of BrowserConsoleHandler:

image

I can make a PR if you find it useful.

Kind regards,

Originally created by @pafernandez-oesia on GitHub (Jul 8, 2022). Original GitHub issue: https://github.com/Seldaek/monolog/issues/1728 Hi! I was just wondering if there is any reason to use `console.log` method for all log levels, instead of also using `debug`, `info`, `warn` and `error` methods depending on the log level. This makes filtering output easier in the browser console and clearly highlights error level messages. The following image shows an example output from Laravel using Monolog and a custom implementation of `BrowserConsoleHandler`: ![image](https://user-images.githubusercontent.com/96843912/177963365-5fa14776-1666-40c4-9a6c-909d36b0e68d.png) I can make a PR if you find it useful. Kind regards,
kerem 2026-03-04 02:17:25 +03:00
  • closed this issue
  • added the
    Feature
         label
kerem commented 2026-03-04 02:17:26 +03:00
Author
Owner
Copy link

@Seldaek commented on GitHub (Jul 22, 2022):

Yeah that sounds good, I think it's mostly because this was done when browser consoles were still pretty basic :)

<!-- gh-comment-id:1192508957 --> @Seldaek commented on GitHub (Jul 22, 2022): Yeah that sounds good, I think it's mostly because this was done when browser consoles were still pretty basic :)
kerem commented 2026-03-04 02:17:26 +03:00
Author
Owner
Copy link

@Seldaek commented on GitHub (Aug 2, 2022):

Fixed by https://github.com/Seldaek/monolog/pull/1739

<!-- gh-comment-id:1202401874 --> @Seldaek commented on GitHub (Aug 2, 2022): Fixed by https://github.com/Seldaek/monolog/pull/1739
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
esfix
2.x
1.x
3.10.0
2.11.0
3.9.0
3.8.1
3.8.0
2.10.0
3.7.0
3.6.0
2.9.3
3.5.0
2.9.2
3.4.0
3.3.1
2.9.1
3.3.0
2.9.0
3.2.0
2.8.0
3.1.0
2.7.0
1.27.1
3.0.0
2.6.0
3.0.0-RC1
2.5.0
2.4.0
1.27.0
2.3.5
2.3.4
2.3.3
2.3.2
2.3.1
2.3.0
1.26.1
2.2.0
1.26.0
2.1.1
1.25.5
2.1.0
1.25.4
2.0.2
1.25.3
2.0.1
1.25.2
1.25.1
1.25.0
2.0.0
2.0.0-beta2
2.0.0-beta1
1.24.0
1.23.0
1.22.1
1.22.0
1.21.0
1.20.0
1.19.0
1.18.2
1.18.1
1.18.0
1.17.2
1.17.1
1.17.0
1.16.0
1.15.0
1.14.0
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.0
1.6.0
1.5.0
1.4.1
1.4.0
1.3.1
1.3.0
1.2.1
1.2.0
1.1.0
1.0.2
1.0.1
1.0.0
1.0.0-RC1
Labels
Clear labels   
Bug

   
Documentation

   
Feature

   
Needs Work

   
Support

   
pull-request

Mirrored from GitHub Pull Request

No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/monolog#724
No description provided.