On Wed, 2018-05-23 at 11:46 +0200, Nicolas Peltier wrote:
> What i'm unclear now is wether we should go the route of a provider
> for
> scripting in general, or "just" pipe (which is my direct interest),
> so
> something like a command where first argument specify a context,
> second is
> the actual script
> g! sling:script groovy println 'Hello World'
> g! sling:script groovy-pipe
> p.echo("/content/site").$("sling:resourceType='bar'").mv("/archives")
>
> or direct
> g! pipe:run
> echo("/content/site").$("sling:resourceType='bar'").mv("/archives")
I would go with the second approach, unless there is a short-term plan
to add more commands.
If we get more gogo shell commands we can always refactor later.
Robert
