Re: SLING_ prefix for selectors that we use "internally" ?

Bertrand Delacretaz wrote > On Tue, Feb 28, 2017 at 11:44 AM, Carsten Ziegeler > wrote: >> ...The script is usually selected by the combination of resource type, >> selector and extension... > > The SlingBindingsVariablesListJsonServlet [1] has to use the >

Re: SLING_ prefix for selectors that we use "internally" ?

Hi But if you insiste on a prefix, I suggest to use something nicer looking than SLING_. How about sling. ? Hence sling.bla such as /path/to/resource.sling.bla.html ? Yet, I agree with Carsten that I am not sure, whether this really is required. On the other hand, using a specific selector

Re: SLING_ prefix for selectors that we use "internally" ?

On Tue, Feb 28, 2017 at 11:44 AM, Carsten Ziegeler wrote: > ...The script is usually selected by the combination of resource type, > selector and extension... The SlingBindingsVariablesListJsonServlet [1] has to use the sling/servlet/default resource type, by design, so I

Re: SLING_ prefix for selectors that we use "internally" ?

Bertrand Delacretaz wrote > Hi, > > The webconsole plugin that was just contributed for In > https://issues.apache.org/jira/browse/SLING-3543 needs a specific > selector to retrieve scripting variables from the HTTP client. > > Currently it's using "SLING_availablebindings" as its selector, with

SLING_ prefix for selectors that we use "internally" ?

Hi, The webconsole plugin that was just contributed for In https://issues.apache.org/jira/browse/SLING-3543 needs a specific selector to retrieve scripting variables from the HTTP client. Currently it's using "SLING_availablebindings" as its selector, with a SLING_ prefix to make collisions with