5 ms·
Just my 2c, but those gaps look too uneven to be produced by a framework. They remind me of my own html from scratch when I didn’t use a formatter or linter hah
by lord_sudo 4y ago
Just my 2c, but those gaps look too uneven to be produced by a framework. They remind me of my own html from scratch when I didn’t use a formatter or linter haha
- justinclift 4y agoYeah, to me they look like the output that I get when I'm writing with Go templates (non-minified afterwards). eg: <html> {{ if eq .FOO "bar" }} <some tags here> {{ end }} <other stuff> {{ if eq .BAZ "bim" }} <some tags here> {{ end }} </html> That ends up generating blank lines all over the place, very much like the output they have. ;)
- mlyle 4y agoThe revision history doesn't seem to support that. They seem to just mash enter a lot. Especially it looks like they have lots of edits where they add blank lines and then another tag, and then remove the new tag but not the blank line. E.g. https://github.com/thstsa/spacetourism/commit/6411ce05009cc69941b0883e379f96e7867d8fa9 https://github.com/thstsa/spacetourism/commit/6411ce05009cc6... Or sometimes just replacing things they intend to outright remove with blank lines. With multiple committers, it seems unlikely they're all templating and then checking in the output of the template engine.
- justinclift 4y agoOh, that's a good point. Yeah, I think you're probably right. :)
- OJFord 4y agoFwiw you can strip the space with: {{- [...] -}} (Or just one side) and put back the right amount with: {{ [...] | [n]indent X }} (Where X is the number of spaces to indent)
- justinclift 4y agoThanks heaps, learn something every day. :)
- deleted 4y ago[deleted]