[ 
https://issues.apache.org/jira/browse/SLING-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253564#comment-15253564
 ] 

ASF GitHub Bot commented on SLING-3543:
---------------------------------------

GitHub user mmanski opened a pull request:

    https://github.com/apache/sling/pull/135

    SLING-3543 solution proposal

    This is a proposal of handling 3543. Console plugin makes real request for 
the selected path with a special selector, which is showing available scripting 
variables for the current path in json format. When we want to access scripting 
variables when for a path that is not supported by any of scripting engines, 
400 is being thrown. 
    
![example](https://cloud.githubusercontent.com/assets/8754944/14736582/2e5cf0b2-0878-11e6-8e18-a2fc2493ce05.png)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mmanski/sling SLING-3543

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sling/pull/135.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #135
    
----
commit 71ab1df006d9ef4eead90798ef4874bcbfbf41af
Author: Mikołaj Mański <[email protected]>
Date:   2015-11-23T09:51:31Z

    Merge pull request #1 from apache/trunk
    
    trunk update

commit 5ac88a052221c8f9db825f6d81c41652bf04c250
Author: Mikolaj Manski <[email protected]>
Date:   2016-04-15T07:25:36Z

    Merge remote-tracking branch 'upstream/trunk' into trunk

commit 0dfaaf220612132f9da9cebf769dc1922736e382
Author: Mikolaj Manski <[email protected]>
Date:   2016-04-22T08:47:04Z

    SLING-3543 introduced mechanism obtaining scripting variables with use of 
bvpvars selector

----


> 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)

Reply via email to