On Fri, May 22, 2009 at 6:04 AM, Martijn Faassen <[email protected]> wrote: > > Hi there, > > On Thu, May 21, 2009 at 5:49 PM, Andy Chu <[email protected]> wrote: >> So the problem with the hooks is that I don't see any use case for >> them that can't be addressed in a way that doesn't modify the core >> code. > > You mean by writing a pre-processor for the templates? That's a lot > more involved than hooking into some hooks, and effectively is a way > to build new languages. json-template is already a template language.
No, I mean by the approach I suggested in my earlier mail. I just sent you a patch in case it's not clear. I can't tell exactly what you're doing without the calling code for your patch. But from your earlier descriptions I think something like my patch will do it. You can get the path info in a similar way. And the logging is definitely not part of the language definition, as it only really exists in JS. I meant to refer to the ScopedContext interface and not the builder interface. Neither one of those is public, although the builder is the one exposed accidentally. Andy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JSON Template" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/json-template?hl=en -~----------~----~----~----~------~----~------~--~---
