AkkomaGang/temple
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
This repository has been archived on 2023-08-07. You can view files and clone it, but cannot push or open issues or pull requests.
temple/CHANGELOG.md
Mitchell Hanberg 265c413960 Allow element attrs to be evaluated at runtime 
Before this change, only keyword list literals could be passed to
elements. If they had non-literals as values, then those would compile
to EEx expressions.

This allows a non-literal to be passed as attrs and have the entire thing
compile to an EEx expression, which will pass the non-literal to a
"runtime_attrs" function, which evaluates a keyword list into a safe
string.

That last part might need to be reworked if the user is not using
the Phoenix.HTML.Engine EEx Engine.
2020-08-09 10:07:27 -04:00

3.1 KiB
Raw Blame History

Changelog

Master

  • Can pass a keyword list to be evaluated at runtime as attrs/assigns to an element.
# compile time

div class: "foo", id: bar do
  # something
end

# <div class="foo" id="<%= bar %>">
#   <!-- something -->
# </div>

# runtime

div some_var do
  # something
end

# <div<%= PrivateTempleModule.runtime_attrs(some_var) %>>
#   <!-- something -->
# </div>

Breaking

Components are now defined using modules. You can convert your existing components by configuring your component prefix and wrapping your current component files in the Temple.Component behaviour implementation.

Bugs

  • Did not correctly parse expressions with do blocks where the expression had two or more arguments before the block

0.6.0-alpha.4

  • Fix a bug where lists would not properly compile

0.6.0-alpha.3

  • Compile functions/macros that take blocks that are not if/unless/for

0.6.0-alpha.2

Component API

Please see the README for more details regarding the Component API

0.6.0-alpha.1

Generators

You can now use mix temple.gen.live Context Schema table_name col:type in the same way you can with Phoenix.

Other

  • Make a note in the README to set the filetype for Live temple templates to lexs. You should be able to set this extension to use Elixir for syntax highlighting in your editor. In vim, you can add the following to your .vimrc
augroup elixir
  autocmd!

  autocmd BufRead,BufNewFile *.lexs set filetype=elixir
augroup END

0.6.0-alpha.0

Breaking!

This version is the start of a complete rewrite of Temple.

  • Compiles to EEx at build time.
  • Compatible with Phoenix.LiveView
  • All modules other than Temple are removed
  • mix temple.convert Mix task removed

0.5.0

  • Introduce @assigns assign
  • Join markup with a newline instead of empty string

0.4.4

  • Removes unnecessary plug dependency.
  • Bumps some other dependencies.

0.4.3

  • Compiles when Phoenix is not included in the host application.

0.4.2

  • temple.convert task no longer fails when parsing HTML fragments.

0.4.1

  • Only use Floki in dev and test environments

0.4.0

  • Temple.Svg module
  • mix temple.convert Mix task
  • (dev) rename mix update_mdn_docs to mix temple.update_mdn_docs and don't ship it to hex

Breaking

  • Rename Temple.Tags to Temple.Html

v0.3.1

  • Temple.Form.phx_label, Temple.Form.submit, Temple.Link.phx_button, Temple.Link.phx_link now correctly parse blocks. Before this, they would escape anything passed to the block instead of accepting it as raw HTML.

v0.3.0

  • Temple.Tags.html now prepends the doctype, making it valid HTML
  • Temple.Elements module

Breaking

  • Temple.Tags.html no longer accepts content as the first argument. A legal html tag must contain only a single head and a single body.

0.2.0

  • Wrap radio_buttton/4 from Phoenix.HTML.Form

0.1.2

Bugfixes

  • Allow components to be used correctly when their module was required instead of imported

0.1.1

Bugfixes

  • Escape content passed to 1-arity tag macros

Development

  • Upgrade various optional development packages

0.1.0

  • Initial Release