You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 18, 2024. It is now read-only.
It would be nice to pass properties from the hook to all contained scripts (e.g. to influence the root node from which to start). Otherwise this information has to be repeated in all contained scripts. For Groovy/Scripting and Sling Pipes one can use bindings for that. I would suggest that nested properties with a specific name are created as bindings automatically
The text was updated successfully, but these errors were encountered:
EDIT: if you are using GroovyConsole script you can set a property data on the parent node of the scripts. The content is interpreted as Json and added to the script as a binding:
Still we should find a way for the other handlers and document the above properly.
very good point, in GroovyConsole scripts there is already a workaround for that:
With slingRequest['scriptPath'] you can access the path of the current script and with that information you can read properties of that node or the parent node via normal means
But you are totally right, a more elegant solution for that would be awesome.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be nice to pass properties from the hook to all contained scripts (e.g. to influence the root node from which to start). Otherwise this information has to be repeated in all contained scripts. For Groovy/Scripting and Sling Pipes one can use bindings for that. I would suggest that nested properties with a specific name are created as bindings automatically
The text was updated successfully, but these errors were encountered: