You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Volker Lamp (Jira)" <ji...@apache.org> on 2022/06/07 20:52:00 UTC

[jira] [Updated] (TAP5-2683) Set MessageFormatter as a service instead of being hardcoded

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

Volker Lamp updated TAP5-2683:
------------------------------
    Issue Type: Improvement  (was: Bug)

> Set MessageFormatter as a service instead of being hardcoded
> ------------------------------------------------------------
>
>                 Key: TAP5-2683
>                 URL: https://issues.apache.org/jira/browse/TAP5-2683
>             Project: Tapestry 5
>          Issue Type: Improvement
>            Reporter: Numa Schmeder
>            Priority: Minor
>
> Currently MessageFormatter is hard coded inside MapMessages. Therefor if you want to change the type of formatter for example using MessageFormat instead of StringFormat your need to override a lot of classes, namely:
>  * MessageSourceImpl
>  * MapMessages
>  * ComponentMessageSourceImpl
>  * MessageFormatterImpl
> It should be easier to override the MessageFormatter instance with a custom one to have specific parsing requirements. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)