[
https://issues.apache.org/jira/browse/SLING-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404753#comment-16404753
]
Radu Cotescu commented on SLING-7515:
-------------------------------------
[~kwin], I cannot think of a way to introduce the behaviour you want without
affecting backwards compatibility for future versions (if we decide to
introduce some other specific block element options) or without reintroducing
the concept of reserved options
(https://github.com/Adobe-Marketing-Cloud/htl-spec/blob/1.0/SPECIFICATION.md#13-reserved-options).
> ResourceRuntimeExtension: Allow to pass arbitrary options a request
> attributes via data-sly-resource
> ----------------------------------------------------------------------------------------------------
>
> Key: SLING-7515
> URL: https://issues.apache.org/jira/browse/SLING-7515
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Scripting HTL Engine 1.0.48-1.3.1
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently it is only possible to pass parameters to another script/servlet
> when using {{data-sly-resource}} with the options to modify the selector
> (https://github.com/apache/sling-org-apache-sling-scripting-sightly/blob/master/src/main/java/org/apache/sling/scripting/sightly/impl/engine/extension/ResourceRuntimeExtension.java).
> It would be good if either all unknown options or only those with a specific
> prefix would be passed as request attributes to the other script/servlet.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
