temple/CHANGELOG.md

# Changelog

## Master

- `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`

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`