tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <...@tapestry.apache.org>
Subject [jira] Commented: (TAPESTRY-1907) The translate parameter is marked as required but it isn't
Date Fri, 04 Jan 2008 15:27:34 GMT

    [ https://issues.apache.org/jira/browse/TAPESTRY-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555941#action_12555941
] 

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

All I'm asking is that the IDE support be as smart as Tapestry is at runtime :-)

Two conflicting pieces here:
- "Smart" defaults (htat allow a default value for translate to be computed, usually, when
value is bound)
- Required parameters, which are invoke a check if not bound (explicitly, or to a smart default)

I know this makes it hard for the IDE, but it makes it very nice for users coding "raw". 
To make required operate the way you'd like, I'd need to strip out smart defaults, forcing
devs to explicitly bind parameters that can be computed.  It would hard, if not impossible,
to determine statically whether a parameter is required or not.  Perhaps the IDE could detect
the corresponding defaultMyParam() method and enforce a "soft required" for such a parameter?

> The translate parameter is marked as required but it isn't
> ----------------------------------------------------------
>
>                 Key: TAPESTRY-1907
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1907
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: Core Components
>    Affects Versions: 5.0.6
>            Reporter: Hugo Palma
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>
> Components like TextField and TextArea have a "translate" parameter that is stated as
being required. But in the documentation it says:
> "If not specified, a value will usually be generated based on the type of the value parameter."
> So, i think the parameter should not be annotated as required as it clearly isn't.

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


Mime
View raw message