parse error with <style> tag #4

dermetfan · 2016-12-22T16:18:52Z

I decided to try ructe for a small web project.

This is a reduced sample that should suffice to reproduce the problem.

main.rs:

include!(concat!(env!("OUT_DIR"), "/templates.rs"));

fn main() {
    templates::style(&mut std::io::stdout()).unwrap();
}

style.rs.html:

@()

<html>
<head>
<style>
#content {
    color: red;
}
</style>
</head>

<body>
<div id="content">Content!</div>
</body>
</html>

This results in a compilation error:

error[E0425]: unresolved name `templates::style`
 --> src/main.rs:4:5
  |
4 |     templates::style(&mut std::io::stdout()).unwrap();
  |     ^^^^^^^^^^^^^^^^

A more informative message is found in target/debug/build/<project>/output:

cargo:warning=Template parse error Eof in "/path/to/project/ructe-issue-3/templates/style.rs.html": "{\n    color: red;\n}\n</style>\n</head>\n\n<body>\n<div id=\"content\">Content!</div>\n</body>\n</html>\n"

The templates compiles if I remove the content of the <style>-tag.

My guess would be that ructe is confused by the curly braces in CSS, as the error message reports an Eof parse error at the first {.

The text was updated successfully, but these errors were encountered:

kaj · 2016-12-22T23:58:32Z

Yes. Since the curly braces are used for delimiting blocks they are not allowed unescaped in templates.

Since there is nothing that would explain a block at that position, it would be possible to actually allow raw curly braces there, but the easy solution is to just escape curly brackets like so:

<style>
#content @{
    color: red;
@}
</style>

dermetfan · 2016-12-23T23:13:49Z

Thanks for the quick clarification! Maybe this should be mentioned in the readme - I couldn't find information on escaping there (other than HTML escaping).

@dermetfan

Add a section about curly brackets to the readme. Suggested by @dermetfan in #4.

kaj · 2017-01-02T13:52:15Z

Yep, it should be in the documentation (such as it is). I added a paragraph to README.md.

@dermetfan

Add a section about curly brackets to the readme (this was originally commited on the feature/staticfiles branch by mistake). Suggested by @dermetfan in #4.

dermetfan · 2017-01-02T16:43:36Z

Great, thanks!

kaj added a commit that referenced this issue Jan 2, 2017

Mention curly brackets escaping.

e444b72

Add a section about curly brackets to the readme. Suggested by @dermetfan in #4.

kaj added a commit that referenced this issue Jan 2, 2017

Mention curly brackets escaping.

ab71207

Add a section about curly brackets to the readme (this was originally commited on the feature/staticfiles branch by mistake). Suggested by @dermetfan in #4.

dermetfan closed this as completed Jan 2, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

parse error with <style> tag #4

parse error with <style> tag #4

dermetfan commented Dec 22, 2016 •

edited

Loading

kaj commented Dec 22, 2016

dermetfan commented Dec 23, 2016 •

edited

Loading

kaj commented Jan 2, 2017

dermetfan commented Jan 2, 2017

parse error with <style> tag #4

parse error with <style> tag #4

Comments

dermetfan commented Dec 22, 2016 • edited Loading

kaj commented Dec 22, 2016

dermetfan commented Dec 23, 2016 • edited Loading

kaj commented Jan 2, 2017

dermetfan commented Jan 2, 2017

dermetfan commented Dec 22, 2016 •

edited

Loading

dermetfan commented Dec 23, 2016 •

edited

Loading