Files
cms-core/Documentation/Changelog/12.3/Deprecation-100047-DeprecatedConditionMatcherClasses.rst
T

51 lines
1.7 KiB
ReStructuredText

.. include:: /Includes.rst.txt
.. _deprecation-100047-1677607925:
==========================================================
Deprecation: #100047 - Deprecated ConditionMatcher classes
==========================================================
See :issue:`100047`
Description
===========
The following classes have been marked as deprecated in TYPO3 v12 and will
be removed with v13:
* :php:`\TYPO3\CMS\Core\Configuration\TypoScript\ConditionMatching\ConditionMatcherInterface`
* :php:`\TYPO3\CMS\Core\Configuration\TypoScript\ConditionMatching\AbstractConditionMatcher`
* :php:`\TYPO3\CMS\Backend\Configuration\TypoScript\ConditionMatching\ConditionMatcher`
* :php:`\TYPO3\CMS\Frontend\Configuration\TypoScript\ConditionMatching\ConditionMatcher`
Impact
======
The TYPO3 Core only uses these classes within the old TypoScript parser classes,
which have been :ref:`deprecated <deprecation-99120-1670428555>` as well.
Using the classes will trigger a deprecation level log entry.
Affected installations
======================
There was probably little need to implement new variants of the above classes as
the underlying :php:`ExpressionLanguage` construct has its own API to add new
variables and functions for this TypoScript condition related to Symfony expression
language usage.
Migration
=========
No direct migration possible. These classes have been merged into the new
TypoScript parser approach, specifically for class
:php:`\TYPO3\CMS\Core\TypoScript\IncludeTree\Visitor\IncludeTreeConditionMatcherVisitor`.
Adding TypoScript related expression language variables and functions should be
done using :php:`\TYPO3\CMS\Core\ExpressionLanguage\ProviderInterface`.
.. index:: PHP-API, FullyScanned, ext:core