v0.14.1

0.14.1 (2025-03-04)

Bug Fixes

• correctly use rest in components (#266) (c772e2d)

Miscellaneous Chores

• release 0.14.1 (d16b312)

v0.14.0

0.14.0 (2024-10-20)

Features

• allow component to declare let! parameter (#245) (a18e6fe), closes #239

Bug Fixes

• allow normal list elements in class attr (#246) (e79e6c7), closes #238

v0.13.1

0.13.1 (2024-10-20)

Bug Fixes

• add mathml tags to formatter (4e8de14)
• void foreign elements get self closing tags (#243) (4e8de14), closes #242

v0.13.0

0.13.0 (2024-10-17)

Features

• add missing and new HTML elements & MathML (#240) (209589e)

v0.12.1

0.12.1 (2024-06-20)

Bug Fixes

• relax constraint on phoenix_html (f28468e)

v0.12.0

0.12.0 (2023-06-13)

⚠ BREAKING CHANGES

• configure runtime attributes function (#202)

Features

• configure runtime attributes function (#202) (dc57221)

Bug Fixes

• docs: typos (7a50587)

v0.11.0

What's Changed

• Align component model with HEEx/Surface by @mhanberg in #182
• Dynamic boolean attributes by @mhanberg in #188
• Dynamic Attributes by @mhanberg in #190

Full Changelog: v0.10.0...v0.11.0

v0.10.0

What's Changed

• feat: Mix task to convert HTML into Temple by @mhanberg in #180
• SVG by @mhanberg in #181

Full Changelog: v0.9.0...v0.10.0

v0.9.0

Full Changelog: v0.8.0...v0.9.0

v0.9.0-rc.0

Breaking Changes

• Requires Elixir 1.13+
• Whitespace control is now controlled by whether you use do/end or :do syntax. The :do syntax will render "tight" markup.
• Components are no longer module based. Any function can now be a component. Now to render a component, you pass a function reference c &my_component/1.
  • Temple.Component has been removed, which removes the render/1 macro for defining a component. Now all you need to do is define a function and have it take an assigns parameter and call the temple/1 macro that is imported from Temple.
  • The defcomp macro has been removed, since now all you need is a function.
• All Phoenix related things and dependencies have been removed. If you are going to use Temple with Phoenix, now use the temple_phoenix package instead.
• Config options have changed. Now all you can configure are the aliases (unchanged from before) and now you can configure the EEx.Engine to use. By default it uses EEx.SmartEngine.

Please see the guides for more in depth migration information.