You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2016/06/30 10:17:10 UTC

[jira] [Resolved] (SLING-5811) Properly handle actual Resources in Sightly data-sly-resource

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

Radu Cotescu resolved SLING-5811.
---------------------------------
    Resolution: Fixed
      Assignee: Radu Cotescu

Fixed in [r1750765|https://svn.apache.org/r1750765].

> 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
>            Assignee: Radu Cotescu
>            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)