calliope
calliope copied to clipboard
An elixir haml parser
Tests are passed ok.
Javascript code following a `:javascript` filter does not get any special treatment, but is tokenized and parsed like regular html code. Therefore calliope will crash or produce incorrect output when...
In the original Ruby Haml implementation, when hash attributes are nil, they're removed from the hash. That is, ```haml - null_var = nil #test{string: "a string", null: nil, null_var: null_var}...
HAML supports json style quoted keys on ruby 2.2, it would be great if calliope would too: ``` haml %meta{"http-equiv": "content-type", "content": "text/html; charset=utf-8"} ```
see https://github.com/phoenixframework/phoenix/issues/2498
Calling render and passing a partial file name should compile. Render partial should also accept arguments. This should be in the similar to the current render but need to test....
This ensures that the attribute parsing goes a little nicer, and at least does not break on the access operator `.` anymore. Note that nested maps are not possible by...
This does not parse correctly: ```elixir iex> Calliope.Render.precompile(".foo{a: 1, b: mystruct.foo, data: %{foo: 3}}") "\n" ``` Note that instead of `mystruct.foo` being escaped, only `mystruct` is escaped. Also note that...
After wasting a bunch of time trying to figure out why all my haml was failing to compile I discovered that the changes between 0.4.1 and 0.4.2 broke a bunch...
`~S/%a(href="#{a} #{b}")/` does not parse correctly. Here is the result of a test case. ``` ** (CalliopeException) Invalid attribute 'href="1{a' on line number 1` stacktrace: (calliope) lib/calliope/parser.ex:183: Calliope.Parser.raise_error/3 (calliope) lib/calliope/parser.ex:140:...