Allow use of parens and brackets in haml content

[davidstump]

Allow use of parens and brackets in haml content

[nurugger07]

Thanks and I appreciate the feedback. This is definitely on the radar. Right now I'm finishing up the engine to precompile the templates so if you want to look at it that would great. Otherwise, I will keep this around and get to it as soon as possible.

[davidstump]

Can't promise any productive results until I am less wide-eyed about Elixir, but I'll definitely keep glancing at it and see if anything seems sane. Otherwise no rush at all, just something I stumbled across.

Cheers!

[nurugger07]

I totally understand :) What resources are you using to learn elixir?

[davidstump]

Finished the nice new Getting Started guide on the site. Was going to check out the elixir sips, otherwise just playing around with it so far. Oh and @chrismccord.

[nurugger07]

Checkout the Etudes book. It's writing little programs to learn the language.

[davidstump]

Wow - that looks incredible. Thanks!

[nurugger07]

No problem. Have fun learning Elixir! It really is great to work with :)

[nurugger07]

Ok I have test cases for this issue & I think I have a solution worked out. If you want to run it through its paces, let me know if you have any more issues.

[davidstump]

Awesome - will do. Thanks again.

[YellowApple]

Stopping by to mention that I'm still running into this issue with Calliope 0.3.0 (the latest, as far as I can tell). So, something like %h1 (foo) gets rendered as <h1 "foo"> instead of the expected <h1>(foo)</h1>. Looks as if Calliope.Parser.parse_line/2 is matching on @parens and @attrs without taking into account whether a HAML tag immediately precedes them. Should I open a new issue for this, seeing as this one is both closed and more than a year and a half old?