Stemming from a discussion here:
the feature would be to address the (good) issue that more and more developers are utilizing Metadata.DisplayText. Unfortunately, there is not a priority mechanism to say which one wins (and there probably
should not be one that the developer can choose since they don't really know what the end user would find to be the most valuable).
As an example of where the "issue" can happen: I added a Title onto the User part and the Username is still being returned (because both User and Title have a Metadata.DisplayText defined). In some instances I could see the username being the most
important, in others, the Title. It just depends on the website (and more specifically) the Content Type.
With this in mind, the thought is to use the power of Tokens and add an additional paramater onto every content type representing the Default DisplayText. Using tokens would give full access to ALL of the Parts/Fields in the Content Type. In addition, if someone
didn't provide a value, it sould just revert back to the use of Display Text as it does today (so there is still a value in the programmer setting up Display Text).
Does this seem a viable approach that could be integrated into the current Display Text? Do you see any performance issues using this approach?