You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2020/01/16 13:58:00 UTC

[jira] [Commented] (SLING-9005) Support ResourceResolver.map() through Sightly

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

Konrad Windszus commented on SLING-9005:
----------------------------------------

This has been discussed during the last hackathon: https://lists.apache.org/thread.html/c80093524461d7203fa9799b79ebbf6bfd1bb3f9795865f4aaf3cd4a%40%3Cdev.sling.apache.org%3E. We should first come up with a new API and then see if there is a dedicated option necessary or whether this can be done automatically (depending on the type of tag).

> Support ResourceResolver.map() through Sightly
> ----------------------------------------------
>
>                 Key: SLING-9005
>                 URL: https://issues.apache.org/jira/browse/SLING-9005
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>    Affects Versions: Scripting HTL Engine 1.3.2-1.4.0
>            Reporter: Henry Kuijpers
>            Priority: Major
>
> It would be very convenient if there is a way to execute ResourceResolver.map(), without having to write Sling Models or other backend logic for this.
> I.e. Sling could provide a way to do so, for example by introducing a helper object, or a provider:
> {code:java}
> ${resourceResolverHelper.map @ path = mySlingModel.path}{code}
> {code:java}
>  ${mySlingModel.path @ map}
> or 
> ${mySlingModel.path @ mapped}
> or 
> ${mySlingModel.path @ resourceResolverMap} 
> {code}
> Can we have a discussion regarding this, to work out an implementation guideline? I could work on creating a PR for this, when we decide the way forward.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)