Inside your tag definition, you could use
tag.render('r:asset:image', tag.attr)
.. assuming you would pass the 'name' attribute to .
You could also create a hash yourself to stand in for tag.attr;
tag.render('r:asset:image', {'name' => 'my_image'})
Could you give some more info on what you'
Thanks for the reply, Jim.
Currently, the parser just skips it (you end up with the tag
output to the browser).
I'll take a look at the link you referenced.
On Wednesday, January 29, 2014 12:52:25 PM UTC-6, Jim Gay wrote:
>
> I don't recall what happens if you have in side a
> tag attribute;
I don't recall what happens if you have in side a
tag attribute; whether or not it's an error or the parser just skips
it.
But I think the way we build tags should be rethought.
They currently are just blocks of procedures, but I played with some
ideas about how to make them more testable and ext
I have written my own simple tag extension as a helper for displaying
blocks of repeating html.
For example, let's say I have this pattern:
first chunk of textsecond chunk of
textthird chunk of text
first chunk of textsecond chunk of
textthird chunk of text
first chunk of textsecond chunk of
