You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Hugo Palma (JIRA)" <de...@tapestry.apache.org> on 2008/01/09 17:03:34 UTC
[jira] Created: (TAPESTRY-2032) Range of integers parameter
semantics should resolve symbols
Range of integers parameter semantics should resolve symbols
------------------------------------------------------------
Key: TAPESTRY-2032
URL: https://issues.apache.org/jira/browse/TAPESTRY-2032
Project: Tapestry
Issue Type: New Feature
Components: Framework
Affects Versions: 5.0.7
Reporter: Hugo Palma
Priority: Minor
Now i can't provide a component parameter with the following value:
1..${maxIndex}
The maxIndex symbol doesn't get resolved. It would be great if Tapestry supported this.
This is specially useful when using the Loop component to iterate over a dynamic number of times.
--
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
[jira] Commented: (TAPESTRY-2032) Range of integers parameter
semantics should resolve symbols
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629326#action_12629326 ]
Howard M. Lewis Ship commented on TAPESTRY-2032:
------------------------------------------------
Is that a symbol or a property?
I think the enhancements I have planned for the expression language will cover this. The ".." operator will allow expressions on either side, which means that you can use constants or properties/method calls.
> Range of integers parameter semantics should resolve symbols
> ------------------------------------------------------------
>
> Key: TAPESTRY-2032
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2032
> Project: Tapestry
> Issue Type: New Feature
> Components: Framework
> Affects Versions: 5.0.7
> Reporter: Hugo Palma
> Priority: Minor
> Fix For: 5.1
>
>
> Now i can't provide a component parameter with the following value:
> 1..${maxIndex}
> The maxIndex symbol doesn't get resolved. It would be great if Tapestry supported this.
> This is specially useful when using the Loop component to iterate over a dynamic number of times.
--
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
[jira] Commented: (TAPESTRY-2032) Range of integers parameter
semantics should resolve symbols
Posted by "Hugo Palma (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629419#action_12629419 ]
Hugo Palma commented on TAPESTRY-2032:
--------------------------------------
Well, in my use case it was actually a property. But it should work with a symbol as well.
Good to know this is already planned. Is there an issue for it that i can follow ?
> Range of integers parameter semantics should resolve symbols
> ------------------------------------------------------------
>
> Key: TAPESTRY-2032
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2032
> Project: Tapestry
> Issue Type: New Feature
> Components: Framework
> Affects Versions: 5.0.7
> Reporter: Hugo Palma
> Priority: Minor
> Fix For: 5.1
>
>
> Now i can't provide a component parameter with the following value:
> 1..${maxIndex}
> The maxIndex symbol doesn't get resolved. It would be great if Tapestry supported this.
> This is specially useful when using the Loop component to iterate over a dynamic number of times.
--
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
[jira] Updated: (TAPESTRY-2032) Range of integers parameter
semantics should resolve symbols
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2032:
-------------------------------------------
Fix Version/s: 5.1
> Range of integers parameter semantics should resolve symbols
> ------------------------------------------------------------
>
> Key: TAPESTRY-2032
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2032
> Project: Tapestry
> Issue Type: New Feature
> Components: Framework
> Affects Versions: 5.0.7
> Reporter: Hugo Palma
> Priority: Minor
> Fix For: 5.1
>
>
> Now i can't provide a component parameter with the following value:
> 1..${maxIndex}
> The maxIndex symbol doesn't get resolved. It would be great if Tapestry supported this.
> This is specially useful when using the Loop component to iterate over a dynamic number of times.
--
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
[jira] Updated: (TAP5-62) Range of integers parameter semantics
should resolve symbols
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-62:
-------------------------------------
Issue Type: Improvement (was: Bug)
> Range of integers parameter semantics should resolve symbols
> ------------------------------------------------------------
>
> Key: TAP5-62
> URL: https://issues.apache.org/jira/browse/TAP5-62
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Reporter: Hugo Palma
> Priority: Minor
>
> Now i can't provide a component parameter with the following value:
> 1..${maxIndex}
> The maxIndex symbol doesn't get resolved. It would be great if Tapestry supported this.
> This is specially useful when using the Loop component to iterate over a dynamic number of times.
--
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
[jira] Closed: (TAP5-62) Range of integers parameter semantics
should resolve symbols
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-62.
------------------------------------
Resolution: Duplicate
Assignee: Howard M. Lewis Ship
> Range of integers parameter semantics should resolve symbols
> ------------------------------------------------------------
>
> Key: TAP5-62
> URL: https://issues.apache.org/jira/browse/TAP5-62
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Reporter: Hugo Palma
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> Now i can't provide a component parameter with the following value:
> 1..${maxIndex}
> The maxIndex symbol doesn't get resolved. It would be great if Tapestry supported this.
> This is specially useful when using the Loop component to iterate over a dynamic number of times.
--
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