[jira] Updated: (TAP5-757) Allow PageLink's "page" parameter to accept page instance or class instead of just logical name to add new type-safe way of render request generation

["Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>]

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

Thiago H. de Paula Figueiredo updated TAP5-757:
-----------------------------------------------

    Summary: Allow PageLink's  "page" parameter to accept page instance or class instead of just logical name to add new type-safe way of render request generation  (was: Allow PageLink's  "page" parameter to accept page instance instead of just logical name to add new type-safe way of render request generation)

Expanding the issue a little bit to support page class instances as a parameter value too.

> Allow PageLink's  "page" parameter to accept page instance or class instead of just logical name to add new type-safe way of render request generation
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-757
>                 URL: https://issues.apache.org/jira/browse/TAP5-757
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Vjeran Marcinko
>
> It's a bit overkill to use ActionLink only for render requests (when no action is needed) just to use its ability to return target page instance from handler methods, preconfigured with required context values. This type safety comes at the expense of 2 HTTP requests.
> If PageLink's "page" parameter could not only accept logical page name, but also page instance, then it would be possible to achieve same type-safety with only one HTTP request.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.