eb0fde6e83
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.
21 lines
299 B
Markdown
21 lines
299 B
Markdown
# Changelog
|
|
|
|
## Master
|
|
|
|
### 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
|