Thanks. That makes sense.
In my case the only thing that raised question marks was the placing of the
error (on execute vs parse)--made it fractionally harder to debug the issue
I was experiencing. From there it caused me to dig deeper and come to the
conclusion that it might be an issue for a
I'm not convinced there is a "why" other than "that's what happens". Feel
free to file an issue.
-rob
On Wed, Jun 22, 2016 at 1:29 PM, Evan Digby wrote:
> Hi Rob,
>
> Thanks! I'm using 1.6. I guess my question wasn't too clear now that I
> read it back.
>
> The question isn't why I can redefin
Hi Rob,
Thanks! I'm using 1.6. I guess my question wasn't too clear now that I read
it back.
The question isn't why I can redefine. More specifically, my question is
why redefining by parsing an empty string returns an error on Execute.
Why can't we redefine a template as empty string? If tha
You don't say what version of Go you are running, but as of Go 1.6,
templates can be redefined, which supports the new 'block' feature.
You are redefining a template, which used to be an error but is not any
more.
-rob
On Wed, Jun 22, 2016 at 1:13 PM, Evan Digby wrote:
> I'm noticing that if
