#110486Debugger does not mark the first blacklisted class as filtered
Description
When a class is the first entry in `DebuggerUtility`‘s class blacklist, its
contents are filtered correctly, but the rendered object header is not marked
as `filtered`.
The header currently searches for the class name in an imploded blacklist and
checks whether its position is greater than zero. A class at the first position
therefore fails this check.
Steps to reproduce:
1. Dump an object using `DebuggerUtility::var_dump()`.
2. Pass its class as the first or only entry in `$blacklistedClassNames`.
3. Observe that the object’s contents are hidden, but its header lacks the
`filtered` marker.
Expected result:
The header is marked as `filtered` for every blacklisted class, independent of
its position in the blacklist.
Actual result:
The first blacklisted class is not marked as `filtered`.
Reviews 2
History 24
-
Wouter Wolters changed description 08/14/26, 18:38
-
Gerrit Code Review pushed patch set 1 for main to change 95334 status
NewUnder Review 08/14/26, 18:39 -
Gerrit Code Review pushed patch set 1 for 14.3 to change 95605 09/03/26, 13:10
-
Wouter Wolters commented and changed status
Under ReviewResolved done0 %100 % 09/03/26, 13:15
Applied in changeset commit:8ac037f2b847a5df0c283cd3e709208a3dfd060a.