The term "static" has been used two different
types of TypoScript sources:
1. Templates added via ExtensionManagementUtility::addStaticFile:
usually Configuration/TypoScript/{constants,setup}.typoscript)
2. Presets from known locations:
ext_typoscript_{constants,setup}.typoscript)
Core-Wise the term "TypoScript preset" for describing
ext_typoscript_constants/setup is new, but coreapi [1]
documenation already uses the same term, therefore we
align the TCA labels and function methods to that (improved)
naming scheme.
Mixing the two types into one term "static" resulted in
sys_template TCA labels which are hard to understand.
Especially the static_file_mode=3 setting – introduced in #22169
and super helpful in order to overwrite ext_typoscript_setup via
Configuration/TypoScript – was impossible to understand without
reading the underlying code, as the flag "static_file_mode" was
described to control static template file inclusion – which of
the mentioned cases? :) – and was mean to
include *static template files* before all *static templates*.
So it boils down to the double use of "static" which makes it
clear that we need a distinct, where "preset" should be fine.
[1] https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FilesAndLocations/Index.html#index-9
TODO:
* Rather drop (breaking!) ext_typoscript_setup/constants and static_file_mode
right away?
* Anyone with in depth knowledge what the fine grained difference was?
Maybe "statics"==preset vs. "static files"==Configuration/TypoScript?
Or was Configuration/TypoScript added later (as an afterthought)
and therefore this mixed terminology arised?