You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/11/27 22:26:35 UTC
[jira] [Commented] (TAP5-2238) When require-ing a module that is
part of a JavaScript Stack, the entire stack should be imported
[ https://issues.apache.org/jira/browse/TAP5-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834164#comment-13834164 ]
ASF subversion and git services commented on TAP5-2238:
-------------------------------------------------------
Commit ee695314fab6794edeeda80bbc9875b6114cfc2a in branch refs/heads/master from [~hlship]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=ee69531 ]
TAP5-2238: When require-ing a module that is part of a JavaScript Stack, the entire stack should be imported
> 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
> 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.1#6144)