tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2238) When require-ing a module that is part of a JavaScript Stack, the entire stack should be imported
Date Tue, 17 Jun 2014 08:33:02 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033553#comment-14033553
] 

Jochen Kemnade commented on TAP5-2238:
--------------------------------------

This only works when the module is imported via {{JavaScriptSupport.require(moduleName)}},
when the module is required on the client-side from within another module, only that module
is loaded instead of the whole stack. I think that should be changed. Maybe have {{ModuleDispatcher}}
redirect to the stack?

> When require-ing a module that is part of a JavaScript Stack, the entire stack should
be imported
> -------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-2238
>                 URL: https://issues.apache.org/jira/browse/TAP5-2238
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.4
>
>
> This is parallel to existing logic w.r.t. to libraries and stacks.
> Without this, it may be necessary to import the stack, and require the desired module,
for efficient behavior in both development and production (with aggregation enabled).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message