Compiler fails to un-escape parser options

[joepie91]

While trying to specify Babel options to Riot without using a .babelrc (I'll be opening a separate ticket about this), I discovered that you can specify options on a <script> tag, to have the options in question passed along to the parser. This doesn't seem to be documented, but it also doesn't work - for example, the following Jade-generated code:

<script options="{&quot;presets&quot;: [&quot;es2015-riot&quot;]}">

... will result in the following error:

Error: ./development/components/app.tag
Module build failed: SyntaxError: Unexpected token &
    at Object.parse (native)
[...]

... failing here due to not un-escaping the "s in the attribute value (which is unsurprising, given that it uses regular expressions to parse it out, rather than a real HTML parser). This should probably be fixed :)

[GianlucaGuarini]

Why do you set the options using the " instead of the regular quotes?

[joepie91]

That's how you're supposed to escape quotes in HTML attributes, per spec, and should thus be supported by anything that attempts to parse HTML attributes. The " escaping in this case is generated by Jade.

[GianlucaGuarini]

ok I got it, but this seems to me more a jade issue pugjs/pug#198

[joepie91]

It's not. It's valid (X)HTML, according to spec, and thus Riot should either support it, or use a standard HTML parser that already supports this.

[GianlucaGuarini]

I will release a patch asap, it seems to me quite easy to fix

[joepie91]

Thanks :)