You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/10/05 14:22:29 UTC

[jira] [Updated] (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:all-tabpanel ]

Jochen Kemnade updated TAP5-2238:
---------------------------------
    Labels: patch  (was: )

> 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
>              Labels: patch
>             Fix For: 5.4
>
>         Attachments: 0001-TAP5-2238-if-a-module-is-requested-that-is-part-of-a.patch
>
>
> 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.3.4#6332)