| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It also always returns an html.Attributes object, instead of
a key/value mapping (which would be provided to html.attributes).
|
|
This is to control e.g. joinChildren.
|
|
|
|
Just always resolving was causing some bugs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I'm not 100% sure the right behavior here in the long run (whether
we should be doing a deep clone or not), so for now I haven't added
any specific tests. Snapshot tests covering uses of templates which
depend on cloning (i.e. parents which reuse a given template) will
do better to make sure everything keeps working like it should.
|
|
|
|
|
|
|
|
|
|
|
|
For now this just returns an empty array, but if we need to make
changes later, it won't require editing all instances of blank
content!
|
|
There's a bad joke to be made about "mutation" versus "mutilation".
|
|
|
|
|
|
This is WIP but seems to be working! Pretty big test of
the new html.template system, which needed some extension
here.
|
