[
https://issues.apache.org/jira/browse/TAP5-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677348#action_12677348
]
Paudi Moriarty commented on TAP5-540:
-------------------------------------
Currently, I'm using a custom BigDecimal Translator which lacks the
localisation features recently introduced. I would prefer not to have to use
internal classes to add those features.
> Allow exact parsing of numeric client input by creating a BigDecimal
> Translator and enabling parseBigDecimal in DecimalFormat
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-540
> URL: https://issues.apache.org/jira/browse/TAP5-540
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Paudi Moriarty
>
> The current NumericTranslator is great but it is not easy to build on it
> since the classes are internal.
> Tapestry should provide a BigDecimal Translator which uses the infrastructure
> created for TAP5-211 but parses client input directly to BigDecimal retaining
> the full precision of that input.
> For example, I need a client input of 100.00 to be translated to a BigDecimal
> with value 100.00. Contributing a NumericTranslator<BigDecimal> results in a
> BigDecimal with value 100 because the input is parsed to a long by the
> NumberFormat before being type coerced.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
