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.

Mitchell Hanberg eb0fde6e83 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 01:09:24 -04:00
..
support	Rename to Temple	2019-07-01 22:48:51 -04:00
temple	Escape content passed to single arity tags	2019-08-07 21:08:16 -04:00
temple_test.exs	Don't recursively call generated component macros (#12)	2019-08-10 01:09:24 -04:00
test_helper.exs	Initial commit	2019-04-14 21:44:39 -04:00