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 2007/10/21 21:25:53 UTC

[jira] Updated: (TAPESTRY-1635) Support for optional validator constraints

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

Howard M. Lewis Ship updated TAPESTRY-1635:
-------------------------------------------

    Fix Version/s:     (was: 5.0.6)
                   5.0.7

> Support for optional validator constraints
> ------------------------------------------
>
>                 Key: TAPESTRY-1635
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1635
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.5
>            Reporter: Dan Adams
>            Assignee: Dan Adams
>             Fix For: 5.0.7
>
>
> I have a validator called 'method' that takes an optional string constraint which defaults to a reasonable value based on the field name. As of 5.0.5 you could do:
> <t:textfield t:id="name" validate="method" />
> you have to do:
> <t:textfield t:id="name" validate="method=" />
> to make the parameter an empty string. otherwise you get an exception that you didn't specify the constraint. I need a way of specifying that this constraint can be optional so you can use it with the first method. Also, I'm not sure if being able to do the second method should be considered a bug since the constraint is required but the value is empty.

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