tkluck/haml.jl

HTML Abstract Markup Language for Julia. Inspired by Ruby's HAML.

haml.jl's Issues

TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.

If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Auto-close (or not) empty/void tags

We should copy Ruby-haml's behaviour.

Support value-less attributes

As reported by @mlhetland in #6. They suggest attr=nothing as a possible way of expressing this, but I'm not sure that's very intuitive as other empty values (e.g. []) mean that the attribute should not be rendered at all. Suggestions welcome.

Preserve whitespace where appropriate

We should copy ruby-haml's behaviour where possible, and possibly make available some similar helper methods/macros.

Be more conservative about attribute escaping

Attribute escaping breaks e.g. charset declarations (at least in firefox), leading to [workarounds like this(https://github.com/tkluck/StatProfilerHTML.jl/blob/109ad6f/haml/index.hamljl#L4). This issue is also reported by @mlhetland in #6 . We could fix this by e.g. only escaping "; maybe there's authoritative behaviour documented somewhere?

Permit syntactic oddities?

I may be missing some mechanism in the current library, but while trying to recreate some existing HTML5, I ran into the following roadblocks (for non-XML HTML5 syntax oddities):

• Equals-signs in attribute values are auto-escaped, which means I can't generate, e.g., content="width=device-width, initial-scale=1".
• Attributes must have values, which means I can't generate, e.g., <script defer …>.
• Tags are always closed (either empty or with a closing tag), which means I can't generate, e.g., <meta charset="utf-8">.

Now, it may be that the more XML-friendly 'width=device-width …', defer="" and <meta …/> are just fine HTML5-wise – so permitting stuff light this might just add unnecessary complication? ¯_(ツ)_/¯

(BTW, for the value-less attributes, I tested using defer=nothing – a solution I've used myself in similar situations, but that seems to have broken the rendering completely, including for the following attributes.)

Be able to iterate keyword arguments passed to template file

The keywords are available using interpolation syntax ($key for when key=42 is passed). We should decide a syntax for iterating over the pairs of key => value.

Allow `Coverage` or `CoverageTools` to act on `hamljl` files

This mostly works in StatProfilerHTML now, but with workarounds and corner cases. We should collect and fix a few of those.

Allow non-closing tags like `meta`

HTML5 allows certain tags as only declarations without /> nor a matching closing tag. One option is to have a whitelist of these tags, but maybe we can also have a syntax for it.

Support more blocks

We currently do not support the following blocks:

• elseif
• function
• begin
• let

These would be interesting additions.