Important: #91079 - Various TypoScriptFrontendRenderer functionality is now internal

Question

Important: #91079 - Various TypoScriptFrontendRenderer functionality is now internal

Closed this issue 2 months ago · 0 comments

https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/10.4/Important-91079-VariousTypoScriptFrontendRendererFunctionalityIsNowInternal.html

Important: #91079 - Various TypoScriptFrontendRenderer functionality is now internal

See 91079

Description

TypoScriptFrontendController has methods and properties which are marked
as "@internal" in TYPO3 v10.

They are still used in TYPO3 v10 from within TYPO3 Core, but extension
authors should use the actual APIs directly.

The properties

TypoScriptFrontendController->sPre
TypoScriptFrontendController->pSetup
TypoScriptFrontendController->all

are related to unpacking TypoScript details related to a page object in
TypoScript and to its caching part, this is now officially marked as
internal - if needed, TemplateService should be queried directly. These
properties will likely be removed in future TYPO3 versions, in order to
decouple TypoScript Parsing from the global
TSFE object.

The properties

TypoScriptFrontendController->additionalJavaScript
TypoScriptFrontendController->additionalCSS
TypoScriptFrontendController->JSCode
TypoScriptFrontendController->inlineJS

and the method TypoScriptFrontendController->setJS() are marked as
internal. The AssetCollector API and the PageRenderer can be used
instead, and TYPO3 Core will move towards these APIs completely
internally.

The property TypoScriptFrontendController->indexedDocTitle is now
marked as internal as the PageTitle API is in place since TYPO3 v9 LTS.

Frontend, ext:frontend