You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Kevin Menard (JIRA)" <de...@tapestry.apache.org> on 2008/03/03 04:26:50 UTC
[jira] Closed: (TAPESTRY-1930) Render missing parameter names in
different font and/or text style.
[ https://issues.apache.org/jira/browse/TAPESTRY-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Menard closed TAPESTRY-1930.
----------------------------------
Resolution: Fixed
Fix Version/s: 5.0.11
> Render missing parameter names in different font and/or text style.
> -------------------------------------------------------------------
>
> Key: TAPESTRY-1930
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1930
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 5.0.6
> Reporter: Kevin Menard
> Assignee: Kevin Menard
> Priority: Minor
> Fix For: 5.0.11
>
> Attachments: TAPESTRY-1930.patch
>
>
> The error message for indicating missing required component parameters could benefit by making the parameter names stand out from the error message better. For example, failing to bind the "object" parameter of the BeanEditForm component yields the following message:
> "Parameter(s) object are required for org.apache.tapestry.corelib.components.BeanEditForm, but have not been bound."
> That entire message renders in a uniform, italicized font. It is simple to misread that message though and not realize that the missing parameter name is "object". If "object" were rendered in a non-italicized font, in a fixed-width font, in bold, or any other differentiator to call attention to it, the error message could be greatly enhanced.
--
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