[jira] Commented: (TAPESTRY-1332) Component parameter report should document alternate types

["Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>]

    [ https://issues.apache.org/jira/browse/TAPESTRY-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479459 ] 

Howard M. Lewis Ship commented on TAPESTRY-1332:
------------------------------------------------

An interesting problem to solve ... from the effectively infinite number of Java classes, how do you identify the ones that can be coerced.  This is also much complicated by the fact that tapestry-component-parameters report does not depend on tapestry-core.

> Component parameter report should document alternate types
> ----------------------------------------------------------
>
>                 Key: TAPESTRY-1332
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1332
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0
>            Reporter: Daniel Gredler
>            Priority: Minor
>             Fix For: 5.0
>
>
> The component parameter report (http://tapestry.apache.org/tapestry5/tapestry-core/component-parameters.html) currently lists the type of each parameter, but there is no way for the user to know what types can be coerced into the parameter type.
> The report should either link to a separate report indicating available coercions, or should list all the possible types for each parameter, based on the standard coercions available in Tapestry.
> A feature that isn't documented might as well not exist, as they say...

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