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

[jira] [Updated] (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 updated TAP5-1942:
---------------------------------
    Labels: bulk-close-candidate  (was: AbstractPropertyOutput Translation)

This issue affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent version of Tapestry (currently 5.4.0, available from Maven Central), please update it as soon as possible and add '5.4.0') to the issue's affected versions.

> 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)