[TASK] Use @import instead of <INCLUDE_TYPOSCRIPT
To be an example of best practice, this patch changes all usages of "<INCLUDE_TYPOSCRIPT ..." to "@import". Tests are adapted as well, as long as they are not tailored to actually test INCLUDE_TYPOSCRIPT syntax. Resolves: #101813 Related: #97816 Releases: main, 12.4 Change-Id: I01c4eb19dfd0106c5577457cd0e1836865112d6a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80797 Tested-by:core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
Showing
- typo3/sysext/core/Tests/Functional/Fixtures/Extensions/test_irre_foreignfield/Configuration/TypoScript/ExtbaseJsonRenderer.typoscript 1 addition, 1 deletion...d/Configuration/TypoScript/ExtbaseJsonRenderer.typoscript
- typo3/sysext/core/Tests/Unit/DataHandling/SoftReference/ExtensionPathSoftReferenceParserTest.php 0 additions, 5 deletions...ng/SoftReference/ExtensionPathSoftReferenceParserTest.php
- typo3/sysext/fluid/Tests/Functional/Fixtures/Extensions/fluid_test/Configuration/TypoScript/Basic.typoscript 15 additions, 4 deletions...ions/fluid_test/Configuration/TypoScript/Basic.typoscript
- typo3/sysext/fluid_styled_content/Configuration/TypoScript/setup.typoscript 25 additions, 27 deletions..._styled_content/Configuration/TypoScript/setup.typoscript
Please register or sign in to comment