You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/01/18 01:49:34 UTC
[jira] Commented: (TAPESTRY-2056) Add configurable null handling
for text fields
[ https://issues.apache.org/jira/browse/TAPESTRY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560184#action_12560184 ]
Howard M. Lewis Ship commented on TAPESTRY-2056:
------------------------------------------------
Part of this fix is to back out some changes that coerced nulls to various flavors of zero.
This introduces a new parameter, nulls, to TextField (and PasswordField and TextArea). The default is to leave nulls alone. It can be set to "zero" to substitute zero for the value instead.
> Add configurable null handling for text fields
> ----------------------------------------------
>
> Key: TAPESTRY-2056
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2056
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0.7
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> Currently, the handling of null values (on the server) and blank values (from the client) is a bit of a mess. Particularily with numeric fields, nulls might mean a blank space, or they might be treated as zero and formatted accordingly. Making this another configurable parameter with smart defaults (ala translate and validate) would be a huge improvement over the current approach (extra coercions from null to various types).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org