temple/CHANGELOG.md

# Changelog

## Master

## 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 `require`d instead of `import`ed

## 0.1.1

### Bugfixes

- Escape content passed to 1-arity tag macros

### Development

- Upgrade various optional development packages

## 0.1.0

- Initial Release
Finishing touches 2019-07-04 00:36:04 +00:00			`# Changelog`

Don't recursively call generated component macros (#12) Recursively calling the macros works fine if you `import` the whole module wherever you are using your components, but not if you `require` the module. This is because importing brings in the all the macros into the callers namespace, which allows them to be called just by the macro name. When you `require` the module, it will look for the generated 2-arity macro in the callers namespace, which probably doesn't exist. We get around this by not recursively calling them and avoiding the problem all togther. A few utility functions solves the original issue of wanting to DRY the file. 2019-08-10 05:09:24 +00:00			`## Master`

Bump v0.5.0 2020-04-09 03:28:02 +00:00			`## 0.5.0`

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

Bump v0.4.4 2020-03-26 17:23:12 +00:00			`## 0.4.4`

			`- Removes unnecessary plug dependency.`
			`- Bumps some other dependencies.`

Bump v0.4.3 2020-01-08 04:49:51 +00:00			`## 0.4.3`

			`- Compiles when Phoenix is not included in the host application.`

Bump v0.4.2 2019-11-23 03:55:57 +00:00			`## 0.4.2`

			`- temple.convert task no longer fails when parsing HTML fragments.`

Bump v0.4.1 2019-09-25 23:23:00 +00:00			`## 0.4.1`

			`- Only use Floki in dev and test environments`

Bump v0.4.0 2019-09-14 01:38:53 +00:00			`## 0.4.0`

Svg module (#25) * Temple.Svg - scopes update_mdn_task to the temple namespace - introduces new temple.convert mix task to convert plain HTML and SVG to Temple syntax * Rename Temple.Tags to Temple.Html * Remove hackney I'm not sure why it was even in there ¯\_(ツ)_/¯ * Update floki * Document temple.convert in README 2019-09-14 01:36:16 +00:00			- `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`

Bump v0.4.0 2019-09-14 01:38:53 +00:00			- Rename `Temple.Tags` to `Temple.Html`
Svg module (#25) * Temple.Svg - scopes update_mdn_task to the temple namespace - introduces new temple.convert mix task to convert plain HTML and SVG to Temple syntax * Rename Temple.Tags to Temple.Html * Remove hackney I'm not sure why it was even in there ¯\_(ツ)_/¯ * Update floki * Document temple.convert in README 2019-09-14 01:36:16 +00:00
Bump v0.3.1 2019-08-28 02:09:22 +00:00			`## 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.

Bump v0.3.0 2019-08-21 03:32:14 +00:00			`## v0.3.0`

Update changelog 2019-08-21 03:17:46 +00:00			- `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`.

Bump v0.2.0 2019-08-13 22:28:28 +00:00			`## 0.2.0`

			- Wrap `radio_buttton/4` from Phoenix.HTML.Form
Add radio_button (#14) 2019-08-13 15:04:14 +00:00
Bump v0.1.2 2019-08-10 05:10:45 +00:00			`## 0.1.2`

Don't recursively call generated component macros (#12) Recursively calling the macros works fine if you `import` the whole module wherever you are using your components, but not if you `require` the module. This is because importing brings in the all the macros into the callers namespace, which allows them to be called just by the macro name. When you `require` the module, it will look for the generated 2-arity macro in the callers namespace, which probably doesn't exist. We get around this by not recursively calling them and avoiding the problem all togther. A few utility functions solves the original issue of wanting to DRY the file. 2019-08-10 05:09:24 +00:00			`### Bugfixes`

			- Allow components to be used correctly when their module was `require`d instead of `import`ed

Bump v0.1.1 2019-08-08 13:01:28 +00:00			`## 0.1.1`

			`### Bugfixes`

			`- Escape content passed to 1-arity tag macros`

			`### Development`

			`- Upgrade various optional development packages`

Finishing touches 2019-07-04 00:36:04 +00:00			`## 0.1.0`

			`- Initial Release`