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

Radu Cotescu updated SLING-5811:
--------------------------------
    Summary: Properly handle actual Resources in Sightly data-sly-resource  
(was: Properly handle actual Resource's in Sightly data-sly-resource)

> Properly handle actual Resources in Sightly data-sly-resource
> -------------------------------------------------------------
>
>                 Key: SLING-5811
>                 URL: https://issues.apache.org/jira/browse/SLING-5811
>             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
>
>
> At the moment Sightly {{data-sly-resource}} expects a resource path. The are 
> moments where we already have a {{Resource}} that we need to include (such as 
> including current resource or iterating and including children) and this 
> leads to conversions such as {{Resource -> path -> Resource}} which are not 
> desirable performance-wise.
> We should properly handle a resource passed as a parameter, such as:
> {code}<sly data-sly-resource="${resource @ resourceType='some/type'}"/>{code}



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

Reply via email to