Feature #52443
closed
new Constants Editor type eint+
0%
Description
The Constants Editor type int+ is not enough. If an integer checkbox is left empty, then it always adds a zero 0 to the constants. This leads to a wrong behaviour in some extensions and to a very long list of zero constants. A zero value is different to a not set empty value.
I propose to add a new type eint+. Empty values will not be added to the constants.
There is already the extension tsparser which implements this feature by XCLASSing the TYPO3 core.
Files
Updated by Mathias Schreiber about 10 years ago
- Target version set to 7.4 (Backend)
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by
Updated by Riccardo De Contardi almost 8 years ago
- Target version changed from 8 LTS to 9.0
Updated by Christian Kuhn over 2 years ago
Hey Franz.
I hope it's ok to close this one: The constant editor parsing has been changed multiple times meanwhile, type validation has been extended. The syntax itself is still ugly and slated for mid-term removal. As such, we shouldn't add more features to it anymore.
If you still have pressing thing we should implement, please look at the comment parser of the new TypoScript parse functionality.
Updated by Christian Kuhn over 2 years ago
- Related to Feature #97816: New TypoScript parser added
Updated by Franz Holzinger over 2 years ago
Hello Christian,
I have been waiting since 2004 to get this missing feature in. And all these 18 years nothing has been done for this case.
Regards,
Franz
Updated by Christian Kuhn about 2 years ago
Hey. I'm sorry this hasn't been tackled, it seems this was not important for many contributors.
I hope you'll agree the base strategy of putting rendering information into TypoScript comments is a rather ugly approach. This is used for the 'constant' editor and the 'extension configuration' currently, I streamlined a lot of this code recently to implement the new TypoScript parser in this area.
Some other persons are working on a new "constant editor" approach - we'll see if it will still make it to TYPO3 v12. This one will drop the "rendering definition via comments" approach. As such, it simply does not make sense to still add new features in this area.