Miha Vrhovnik
Miha Vrhovnik
I can do an import (thanks for the hint)that's no problem, but the panic remains and it would be nice if it would be fixed and an error reported instead.
> I agree with you – what would you say should the error message be "label not defined in this context". The same error or something very similar is already...
edit: The error is unexpected "|" in command. > Also, you may want to try the plain old function invocation syntax which should work inside the yield as T("Email", etc.)...
Even though that you don't like the translate version example... there is the same issue if one want's to use "default" in pipelinig fashion. e.g ` {{yield inputField(id="email", name="email", type="email",...
Below are 4 examples and before reading an answer try to figure out which ones should work. ``` var data jet.VarMap data.Set("errs", make(map[string]string)) {{block test1(error="")}} {{if isset(error) && error}} {{error}}...
FYI: the twig/jinja etc use ~ as a concat operator. I don't know if this is reserved here, but It's more readable than the dot as dot can easily be...
Just start coding and provide a PR per feature.
You can't do uploads from javascript with custom headers.
I added the CDATA support. At the time it was deemed to be to expensive to test each string if can be serialized without putting it in CDATA
I'm not fond of incrementing it, because when importing a million records the UUIDs are already close together just incrementing the random part wouldn't help much on that regard.