[
https://issues.apache.org/jira/browse/SLING-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251620#comment-15251620
]
Mikołaj Mański commented on SLING-3543:
---------------------------------------
What about providing a console tab with input for the user, where he can type a
path to check what scripting variables are available under it? Then we could
make a request for the page with some selector that would expose all scripting
variables available and show them? It could be useful when someone would
dynamically adjust his variables depending on a specific context (like site,
scripting engine etc.) and we wouldn't have to gather variables from all
scripting engines, but just for the one which is handling a particular
resource. Additionally, providing a selector to a specific page would result in
showing all scripting variables as json. What do think about this?
> 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: Improvement
> 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.3.4#6332)
