Unify modes for "Display constants" in TS object browser
The different modes for displaying constants in the backend modul "Template / Object browser" could be unified by displaying the "substituted constants in green" and having the "unsubstituted constants" as a title attribute. then one wouldnt have to change between those two modes anymore and since "Plain substitution" is redundant anyway, we could get rid of the entire feature of having different modes at all ;-)
[FEATURE] Display (un)substituted TS constant
Display value of TS constants on "UN-substituted constants in green"
mode and constant name when on "Substituted constant in green" mode.
Before this patch toggling between both modes was necessary to simply
get an idea of what the value/variable name was while being on the
As a side effect this patch improves the search feature of the object
browser when searching for a constant value or name, i.e. 'maxWInText'
while being on "Substituted" mode.
Reviewed-by: Benni Mack <firstname.lastname@example.org>
Tested-by: Benni Mack <email@example.com>
Tested-by: TYPO3com <firstname.lastname@example.org>
Reviewed-by: Susanne Moog <email@example.com>
Tested-by: Susanne Moog <firstname.lastname@example.org>
#1 Updated by Jigal van Hemert over 6 years ago
- Category set to Backend User Interface
- Priority changed from Should have to Could have
- Target version set to 6.1.0
It's a change in the UI so it can only go in 6.1. We probably have to find a better way than the title to display the unsubstituted constants.
#3 Updated by Philipp Kitzberger over 4 years ago
What about clicking on the green substituted string to find out about the unsubstituted variable name? Toggle in an overlay? Along with a link to the ts-browser in constant mode?
Is anyone going to rewrite the whole ts object browser?
#7 Updated by Philipp Kitzberger over 2 years ago
After 4 years of waiting and being annoyed that I still have to toggle between "UN-substituted constants in green" and "Substituted constants in green" whenever I was working with the TS object browser, I today dug out this ancient issue and wrote a tiny patch to tackle this once and for all.
Please be merciful with your review and include this patch to the core ;-)