[PR #58] [MERGED] Added a ChromePhpHandler. #906

New issue

Closed

opened 2026-03-04 03:02:36 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 03:02:36 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Seldaek/monolog/pull/58
Author: @stof
Created: 2/19/2012
Status: ✅ Merged
Merged: 2/20/2012
Merged by: @Seldaek

Base: master ← Head: chromephp

📝 Commits (2)

e3e2bb2 Added a ChromePhpHandler.
68702d3 Detect Chrome through the user agent in ChromePhpHandler

📊 Changes

7 files changed (+466 additions, -1 deletions)

View changed files

📝 CHANGELOG.mdown (+1 -0)
📝 README.mdown (+2 -0)
➕ src/Monolog/Formatter/ChromePhpFormatter.php (+77 -0)
➕ src/Monolog/Handler/ChromePhpHandler.php (+127 -0)
➕ tests/Monolog/Formatter/ChromePhpFormatterTest.php (+158 -0)
📝 tests/Monolog/Functional/Handler/FirePHPHandlerTest.php (+3 -1)
➕ tests/Monolog/Handler/ChromePhpHandlerTest.php (+98 -0)

📄 Description

Closes #56

Currently, the handling of the context is done in the same way than for FirePHP: sending an array containing the message, the context and the extras.
The header is used for all browser so it will face the same issue in IE than the original FirePHPHandler implementation. But I haven't seen a way to determine if the extension is activated or no when looking at the request header. It would probably require some changes in the ChromePHP side to add a request header. @ccampbell do you think it could be possible ?

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Seldaek/monolog/pull/58 **Author:** [@stof](https://github.com/stof) **Created:** 2/19/2012 **Status:** ✅ Merged **Merged:** 2/20/2012 **Merged by:** [@Seldaek](https://github.com/Seldaek) **Base:** `master` ← **Head:** `chromephp` --- ### 📝 Commits (2) - [`e3e2bb2`](https://github.com/Seldaek/monolog/commit/e3e2bb2f4fc7d62b88228cfbe25e96743fface87) Added a ChromePhpHandler. - [`68702d3`](https://github.com/Seldaek/monolog/commit/68702d3bfaacd3e1431a724c3aba6cb05fb2d0c7) Detect Chrome through the user agent in ChromePhpHandler ### 📊 Changes **7 files changed** (+466 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `CHANGELOG.mdown` (+1 -0) 📝 `README.mdown` (+2 -0) ➕ `src/Monolog/Formatter/ChromePhpFormatter.php` (+77 -0) ➕ `src/Monolog/Handler/ChromePhpHandler.php` (+127 -0) ➕ `tests/Monolog/Formatter/ChromePhpFormatterTest.php` (+158 -0) 📝 `tests/Monolog/Functional/Handler/FirePHPHandlerTest.php` (+3 -1) ➕ `tests/Monolog/Handler/ChromePhpHandlerTest.php` (+98 -0) </details> ### 📄 Description Closes #56 Currently, the handling of the context is done in the same way than for FirePHP: sending an array containing the message, the context and the extras. The header is used for all browser so it will face the same issue in IE than the original FirePHPHandler implementation. But I haven't seen a way to determine if the extension is activated or no when looking at the request header. It would probably require some changes in the ChromePHP side to add a request header. @ccampbell do you think it could be possible ? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>