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
{{ message }}
This repository was archived by the owner on Apr 25, 2018. It is now read-only.
I didn't think that was valid but thats actually what is supposed to be done, it turns out, so we SHOULDN'T be using ~> for script attributes (script tags are another story.)
I think it's still a good idea to keep ~> in case you want to inline some html instead of emerald, but we should discourage using it for script attributes. We also need to investigate if any special escaping has to be done for script tag contents or if we an still use => there.
We need to make sure that:
should become:
...but, here's the weird thing. If we're doing a code block:
that should actually become:
I didn't think that was valid but thats actually what is supposed to be done, it turns out, so we SHOULDN'T be using
~>for script attributes (script tags are another story.)I think it's still a good idea to keep
~>in case you want to inline some html instead of emerald, but we should discourage using it for script attributes. We also need to investigate if any special escaping has to be done for script tag contents or if we an still use=>there.