[ https://issues.apache.org/jira/browse/SLING-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-3543: ----------------------------------- Attachment: Scripting_Variables_Web_Console.png SLING-3543-v01.patch Attached is a patch mostly based on the work from [~mikolaj.man...@cognifide.com]. It adds a new web console tab as shown in !Scripting_Variables_Web_Console! It exposes all scripting variables by sending a request towards a given resource (via Ajax). We cannot really prevent that additional request, because the scripting variables depend heavily on the context (i.e. which resource it is). [~bdelacretaz] Can you have a look? > 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 > Assignee: Konrad Windszus > Attachments: Scripting_Variables_Web_Console.png, SLING-3543-v01.patch > > > 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.15#6346)