---
title: "Feature: #100586 - Null-safe operator in TypoScript conditions"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-100586-1681464016"
source: "Changelog/12.1/Feature-100586-Null-safeOperatorInTypoScriptConditions.rst"
typo3-version: "12.1"
typo3-major: 12
type: "feature"
issue: 100586
forge: "https://forge.typo3.org/issues/100586"
tags: ["Backend", "Frontend", "TypoScript", "ext:core"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Feature: #100586 - Null-safe operator in TypoScript conditions {#feature-100586-1681464016}

See [forge#100586](https://forge.typo3.org/issues/100586)

## Description {#description}

By raising TYPO3's Symfony dependencies to `6.2` in [forge#99239](https://forge.typo3.org/issues/99239), a couple
of new features were made available for the [expression language](https://symfony.com/doc/current/reference/formats/expression_language.html), which is
used by TYPO3 for its [TypoScript conditions](https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Conditions/Index.html#conditions).

One of those new features is the [null-safe operator](https://symfony.com/doc/current/reference/formats/expression_language.html#null-safe-operator). This operator is
especially useful when accessing properties on objects, which however might
not be available in some context, e.g. "TSFE" in the backend.

TYPO3 designed its custom expression functions in a way that they support the
usage of the null-safe operator by default. This is done by returning
`NULL` in case the requested object is not available.

Therefore, instead of `[getTSFE() && getTSFE().id == 123]`,
integrators can simplify the condition to `[getTSFE()?.id == 123]`.

## Impact {#impact}

It's now possible to simplify TypoScript conditions using the new expression
language features, especially the null-safe operator.