AkkomaGang/temple
Archived
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases 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 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

299 B
Raw Blame History

Changelog

Master

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