It might be handy to have transforms called with a context that gives them automagic access to the gobble instance that is calling them (in my case for env()). Also handy would be a way to log what's going on in a gobble-friendly in the midst of a long-ish-running transform. Perhaps something like this.log()? console.log is not very pretty jumping in between all the pacman dots :-)
Yes, this makes sense - though I reckon it should be readonly (i.e. this.env rather than this.gobble.env(), which by definition would allow this.gobble.env('mwhahah')). I like the this.log() idea as well
It might be handy to have transforms called with a context that gives them automagic access to the gobble instance that is calling them (in my case for
env()
). Also handy would be a way to log what's going on in a gobble-friendly in the midst of a long-ish-running transform. Perhaps something likethis.log()
?console.log
is not very pretty jumping in between all the pacman dots :-)