[
https://issues.apache.org/jira/browse/SLING-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989444#comment-13989444
]
Konrad Windszus commented on SLING-3543:
----------------------------------------
I agree, that the script engines tab should be fine for that. It should expose
which variables (name and type) are exposed through which service (if possible).
This is especially useful in the context of Sling Models, as there you have to
know what can be injected from the BindingsInjector.
> Provide a Felix Web Console Tab exposing the available Scripting Variables
> --------------------------------------------------------------------------
>
> Key: SLING-3543
> URL: https://issues.apache.org/jira/browse/SLING-3543
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting Core 2.0.26
> Reporter: Konrad Windszus
>
> Currently you can very dynamically define the scripting variables
> (https://cwiki.apache.org/confluence/display/SLING/Adding+New+Scripting+Variables).
> Therefore it would be very good to expose which variables are exposed within
> each script provider in a dedicated web console tab.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
