Deprecation Collector
Captures PHP deprecation notices with message, source location, category, and stack trace.

What It Captures
| Field | Description |
|---|---|
time | Timestamp of the deprecation |
message | Deprecation message |
file | File where the deprecation was triggered |
line | Line number |
category | Deprecation category |
trace | Stack trace |
Data Schema
[
{
"time": 1711878000.123,
"message": "Method getData() is deprecated, use getResult() instead",
"file": "/app/src/Legacy/Service.php",
"line": 55,
"category": "user",
"trace": [...]
}
]Summary (shown in debug entry list):
{
"deprecation": {
"total": 2
}
}Contract
The collector registers a custom PHP error handler that intercepts E_DEPRECATED and E_USER_DEPRECATED notices. No explicit collect() method is needed — deprecations are captured automatically.
INFO
DeprecationCollectorAppDevPanel\Kernel\Collector\DeprecationCollectorCollects Deprecation data during application lifecycle. implements SummaryCollectorInterfaceAppDevPanel\Kernel\Collector\SummaryCollectorInterfaceSummary data collector responsibility is to collect summary data for a collector. Summary is used to display a list of previous requests and select one to display full info. Its data set is specific to the list and is reduced compared to full data collected in {@see CollectorInterface}. and depends on TimelineCollectorAppDevPanel\Kernel\Collector\TimelineCollectorCollects Timeline data during application lifecycle..
How It Works
On startup(), the collector registers a PHP error handler via set_error_handler(). All deprecation warnings (E_DEPRECATED, E_USER_DEPRECATED) are captured with full stack traces. The original error handler is restored on shutdown().
Debug Panel
- Deprecation list — all deprecation notices with message and source location
- Stack traces — expandable trace for each deprecation
- File links — clickable source paths for IDE integration