[
https://issues.apache.org/jira/browse/SLING-10096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284821#comment-17284821
]
Robert Munteanu commented on SLING-10096:
-----------------------------------------
Thanks for the context [~santiagozky]. I think exporting an API is fine for
this scenario. Could this be done as a separate, new, package, so we avoid any
conflicts with the old exports and start with a minimal API surface?
> Allow the SlingHttpServletRequest in the IncludeGenerator or Sling dynamic
> includes
> -----------------------------------------------------------------------------------
>
> Key: SLING-10096
> URL: https://issues.apache.org/jira/browse/SLING-10096
> Project: Sling
> Issue Type: Improvement
> Reporter: Santiago García Pimentel
> Priority: Major
>
> The current interface of the IncludeGenerator of Sling Dynamic Includes only
> pass the String with the original URL.
> It would be great to allow to pass it also the Request to allow clients to
> implement more robust/complex implementations.
> For example, allow to create SDI that use the information of the user making
> the request
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
