[jira] [Commented] (SLING-5812) Add option to include attributes in request scope for Sightly data-sly-request and data-sly-include

["Vlad Bailescu (JIRA)" <ji...@apache.org>]

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

Vlad Bailescu commented on SLING-5812:
--------------------------------------

Created a pull request at https://github.com/apache/sling/pull/149

Patch available at https://patch-diff.githubusercontent.com/raw/apache/sling/pull/149.patch

> Add option to include attributes in request scope for Sightly data-sly-request and data-sly-include
> ---------------------------------------------------------------------------------------------------
>
>                 Key: SLING-5812
>                 URL: https://issues.apache.org/jira/browse/SLING-5812
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>    Affects Versions: Scripting Sightly Engine 1.0.18
>            Reporter: Vlad Bailescu
>            Priority: Minor
>             Fix For: Scripting Sightly Engine 1.0.20
>
>
> A common pattern for sending information between scripts/components is setting specific attributes in request scope before including another resource or script. At the moment this cannot be done nicely in Sightly.
> It would be very helpful to set request attributes as in following examples:
> {code}<sly data-sly-include="${'script.html' @ requestAttributes=helper.attributesMap}"/>{code}
> or:
> {code}<sly data-sly-resource="${'some/path' @ resourceType='some/type', requestAttributes=helper.attributesMap}"/>{code}
> where {{attributesMap}} is a {{Map<String, Object>}}
> The attributes would be set before the actual script/resource inclusion and reset/unset back afterwards.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)