#111509Make most of the backend null-safe
Description
The JavaScript of the backend reads values that can be missing at runtime without a check. Most of it follows the shape the other extensions showed: lookups of elements the module renders itself are declared as if they always succeed, dataset attributes are used as strings although a missing one yields undefined, and indices are built from values that may not be there.
Some declarations are untrue as well. Parameters with a null default declare a type that does not admit null, so every caller has to work around them. The TypoScript stream parser models its scratch state, its variable chain and its context chain as always present, although all three start as null and are walked until null. Its combinators are pushed on a stack and invoked generically, yet the stack claims to know their arguments. The module menu reads the top level TYPO3 object through an optional chain and then treats the result as always set.
These places should get a guard or a fallback where the value can really be missing, and a correct declaration where it was wrong. What the backend still reports afterwards is a long tail without a shared shape and is left to a follow-up.
Reviews 1
History 02
-
Gerrit Code Review pushed patch set 9 for main to change 95431 status
NewUnder Review <span data-processor="relativetime" data-value="2026-11-19T14:43:40+00:00" > 11/19/26, 14:43 </span> -
Gerrit Code Review pushed patch set 10 for main to change 95431 <span data-processor="relativetime" data-value="2026-11-20T10:55:41+00:00" > 11/20/26, 10:55 </span>