| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
The rationale was explained on the mailing list[1].
[1]: https://paste.thomasvoss.com/353
|
| |
|
|
|
|
| |
I cannot think of a single situation where you’d ever end up in this
situation, and I also am not even sure if it’s even meant to be legal
HTML. Better to be on the safe side I guess.
|
| |
|
|
|
|
|
|
|
| |
Well well well, here we are again.
Iterate over the `nClasses` list instead of every attr after printing
the classes.
With all due respect, you should consider writing a test suite to catch
silly errors like this.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There's a bug in the current version of GSP where an element like this:
p .class attribute="value" {-}
would be transpiled as this:
<p class="value" attribute="value"></p>
The `classes` slice in `func printAttrs` (`formatter.go`, line 50) was
the cause. I fixed it by making a deep copy of the `attrs` slice. I'm not
a Go programmer, there might be a nicer way to make a deep copy of a slice.
But it does, indeed, work.
P.S. thanks for making this, writing HTML by hand is now slightly less
painful!
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
