You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the spirit of "test first" methodology I made a breaking test first,
expected: "<foo class=\"first second third\">content</foo>\n"
but got: "<foo class=\"first\" class=\"second\" class=\"third\">content</foo>\n"
When I was inspecting results in a browser from a client's application it looked more like <foo class="first">
Any hoodle, since class is a cdata-list it seems to me like the justification for space separated concatenation is there. I'd like to be able to programmatically inject additional classes into my markup using the *{...} syntax.
The text was updated successfully, but these errors were encountered:
After some review: it looks like this will require too much refactoring to make it work as described. This is a good change, and if someone wants to take a stab at it, I got some initial work on this in bcc1cbf.
For posterity's sake in case anyone else needs quick fix, I injected the additional classes as space-separated text values in Hamlet using the normal #{...} syntax rather than using [(Text, Text)] and *{attrsVarName}.
In the spirit of "test first" methodology I made a breaking test first,
When I was inspecting results in a browser from a client's application it looked more like
<foo class="first">
Any hoodle, since
class
is acdata-list
it seems to me like the justification for space separated concatenation is there. I'd like to be able to programmatically inject additional classes into my markup using the*{...}
syntax.The text was updated successfully, but these errors were encountered: