You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2016/08/22 06:48:22 UTC

[jira] [Closed] (TAP5-1942) AbstractPropertyOutput should use Translator to render values

     [ https://issues.apache.org/jira/browse/TAP5-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade closed TAP5-1942.
--------------------------------
    Resolution: Incomplete

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.4.1 or newer), feel free to provide the necessary information and reopen.

> AbstractPropertyOutput should use Translator to render values
> -------------------------------------------------------------
>
>                 Key: TAP5-1942
>                 URL: https://issues.apache.org/jira/browse/TAP5-1942
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3.3
>            Reporter: Sascha Dömer
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> The AbstractPropertyOutput uses the simple *.toString() representation for object rendering:
> String text = value == null ? "" : value.toString();  // line 134 in AbstractPropertyOutput.java
> This can be a good solution if there is no translator necessary. But in case you'd like to render dates, formatted numbers or other custom output it would be nice, if the configured translators have an effect at this point.
> Of course the representation can be adjusted using a single block, but using the translator for property output would be fitting really nice within the concepts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)