[NFR]: History Panel enhancements
维护者通常 3 天内回复
@niden 已经在做这个了。
开始于 2026年9月26日。
评估
这个 Issue 还没有评估数据。
描述
Additional enhancements after #23 is merged
The history cookie is set without a headers_sent()
(src/DebugBar/History/HistoryCookie.php:61, called from src/DebugBar/ResponseListener.php:73-78)
Sometimes output starts before beforeSendResponse. Examples: a deprecation notice in bootstrap with display_errors on, or echo/var_dump with useImplicitView(false) when output_buffering=0. output_buffering=0 is PHP's default when there is no php.ini, as in the official Docker images.
- In that case,
setcookie()gives an E_WARNING. The package's ownPhalcon\Debug::listenLowSeverity()(src/Debug.php:191,252-254) turns that warning into aRuntimeWarningexception inside the listener, so the user sees an error page instead of the page.
This happens on the first allowed response of each browser. Before this PR, the listener made no native header calls, and Phalcon's sendHeaders() skips silently in this case.
Options:
- (a) Return early in HistoryCookie::queue() when headers_sent() is true. Inject the check like $setCookie so tests can cover both paths.
- (b) Skip record() and queue() in ResponseListener when headers_sent() is true.
The query string is stored on disk without redaction
(src/DebugBar/ResponseListener.php:102, src/DebugBar/Collector/RequestCollector.php:65-68)
meta.uri stores the raw getURI(), for example /reset?token=abc. The Query section masks token, but the raw URI keeps the value. This goes around redact.mask.
We have three new places for the URI:
- metrics.uri
- the history list
- disk storage (the sidecar and the payload), kept for ttl_seconds (24 h by default).
Options:
- (a) Store only the path in the metadata (getURI(true), which exists on the v5 and v6 RequestInterface). In RequestCollector, send the parsed query through the Redactor and rebuild the URI for the URI row and metrics.uri.
- (b) Give the Redactor to the code that builds RequestMetadata, and store a redacted URI (parse_str → redact → http_build_query).
ResponseListener holds the history workflow
(ResponseListener.php:49-51, 61-78, 96-143; Provider.php:90-92, 170-199, 288-329)
The constructor now has 9 parameters. registerHistory() sets two nullable properties as a side effect, and then boot() checks both again.
Options:
- (a) Move the history steps into a new History\HistoryRecorder with isEndpointRequest() and record(...). ResponseListener then takes one ?HistoryRecorder, registerHistory() returns it, and the two properties go away.
- (b) Keep the listener as it is, but make registerHistory() return a small readonly object (history, endpoint, cookie) instead of setting properties.
The endpoint can hide application routes
(src/DebugBar/History/HistoryOptions.php:87-95)
history.url = '/' passes validation and sends the home page to the history controller. Any value that is the same as an application route replaces that route without a warning.
Options:
- (a) Reject / in validate().
- (b) Document that the endpoint wins over an application route with the same path.
CHANGELOG
Some behavior changes are not listed:
- meta.widgets is now sent, so the logger tab now reads "Logs" instead of "Logger", and panel types are declared instead of guessed.
- Time moved from a tab to an indicator.
Options:
- (a) Remove the "Fixed" block, undo the change on line 60, and add a "Changed" entry.
- (b) Merge the "Fixed" items into "Added", and add the "Changed" entry.
Long positional parameter lists in JS
(resources/assets/debugbar.js:110, 417)
renderIndicators takes 7 positional parameters and renderHistoryBrowser takes 6. The call sites are hard to read, and it is easy to put the arguments in the wrong order.
Options:
- (a) Pass one options object.
- (b) Split renderIndicators into renderMetricIndicators and renderRequestControl.
max browsers
It seems that max browsers reflects the max number of files PER browser and not how many browsers are open. Investigate if this is true or not. If it is, the name must change because any future developer will derive that this is an actual max browser windows vs files per browser.
- 主要语言
- PHP
- 星标
- 6
- 派生
- 3
- 平均合并
- 1 天 17 小时
- 30 天内合并 PR
- 3
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
phalcon/debugbar 的其他 Issue
-
[NFR]: Collector source adapters for ADR data sources (DB / View / Route)可能重新可做 @niden 于 78 天前认领,目前没有进行中的 PR。 未关闭enhancement
phalcon/debugbar#16 · 已指派 1 人 ·
维护者通常 3 天内回复
-
[NFR]: Decouple collectors from framework event names (bridge + canonical signals)可能重新可做 @niden 于 78 天前认领,目前没有进行中的 PR。 未关闭enhancement
phalcon/debugbar#15 · 已指派 1 人 ·
维护者通常 3 天内回复
-
[NFR]: Framework-neutral integration seam: boot and response injection without Mvc\Application可能重新可做 @niden 于 78 天前认领,目前没有进行中的 PR。 未关闭enhancement
phalcon/debugbar#14 · 已指派 1 人 ·
维护者通常 3 天内回复
-
[NFR]: Debug bar support for ADR / non-MVC apps可能重新可做 @niden 于 78 天前认领,目前没有进行中的 PR。 未关闭enhancement
phalcon/debugbar#13 · 已指派 1 人 ·
维护者通常 3 天内回复
-
[NFR]: Services panel for DebugBar可能重新可做 @niden 于 88 天前认领,目前没有进行中的 PR。 未关闭enhancement
phalcon/debugbar#5 · 已指派 1 人 ·
维护者通常 3 天内回复
相似的 Issue
-
maintenance
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
hawk-digital-environments/HAWKI#443 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
crazy-goat/rabbit-stream#799 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
-
Code Quality
难度 2/5 1-3 小时 新手友好度 76/100
Automattic/safe-publish#708 ·
维护者通常 1 天内回复