Project

General

Profile

Actions

Bug #99268

closed

Streamline centralized to load TSconfig

Added by Daniel Siepmann over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend API
Target version:
-
Start date:
2022-12-05
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

#96614 introduced a new way to load PageTSConfig. This is now out of sync with loading UserTSConfig.
This will probably lead to frustration in intragrator and developer side as they can't follow one approach for TSconfig but need to use the old one for UserTSconfig while there is a newer for PageTSconfig.

I would propose to streamline the loading and add the same way to User TS config as well before 12 LTS release.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #96614: Add centralized way to load PageTsConfigClosedBenni Mack2022-01-21

Actions
Blocked by TYPO3 Core - Task #99120: Deprecate old TypoScriptParserClosed2022-11-17

Actions
Actions #1

Updated by Daniel Siepmann over 1 year ago

  • Related to Feature #96614: Add centralized way to load PageTsConfig added
Actions #2

Updated by Daniel Siepmann over 1 year ago

  • Blocked by Task #99120: Deprecate old TypoScriptParser added
Actions #3

Updated by Christian Kuhn about 1 year ago

  • Status changed from New to Resolved

There is now a factory for PageTsConfig and a factory for UserTsConfig in core/TypoScript. The casual consumer API remains to be BackendUtility::getPagesTsConfig() and BackendUserAuthentication->getTSConfig(), the factories probably only need to be called in special cases.

Actions #4

Updated by Benni Mack about 1 year ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF