Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[NFR]: Debug bar support for ADR / non-MVC apps

未关闭
#13 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 3 天内回复

@niden 已经在做这个了。

开始于 2026年7月22日。

评估

这个 Issue 还没有评估数据。

描述

enhancement

Context: phalcon/debugbar can only be booted and injected against a Phalcon\Mvc\Application, and its collectors gather data by subscribing to MVC event names. That makes the bar unusable in an ADR app (Phalcon\ADR), which was discovered while wiring phalcon/vokuro-adr (the bar is a dependency there but entirely unused). The goal is to make the bar work on ADR - and, by construction, on any framework - without forcing Phalcon\Di\DiInterface back into the ADR delivery ring. Motivation: ADR is a strong pattern for HTML apps, not only JSON, and the debug bar should not be MVC-only.

Events-manager strategy #15

The root coupling is that collectors know framework event names. Break it with three layers:

  1. A canonical debug-bar signal set the bar owns — a small, stable vocabulary (query, view.rendered, route.matched, request.received, response.sending). Collectors subscribe only to these.
  2. A per-framework bridge that maps native signals to canonical ones — MVC listens to db:afterQuery / view:* / router:matchedRoute; ADR listens to PIPELINE_* / APPLICATION_* or instruments directly.
  3. A direct push API on collectors for hosts with no events manager — the bridge pushes.

The events manager then becomes an implementation detail of the active bridge, not a hard dependency of the collectors.

主要语言
PHP
星标
6
派生
3
平均合并
1 天 17 小时
30 天内合并 PR
3

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

phalcon/debugbar 的其他 Issue

查看 phalcon/debugbar 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。