* Move directories for ast tests to match convention
* feat!: Rename `:let` to `:let!`
We use the "bang" style as the reserved keyword to differentiate it from
other possible attributes.
* feat: use Phoenix.HTML as the default engine
I am choosing to leverage this library in order to quickly get dynamic
attributes (see #183) up and running.
This also ensures that folks who wish to use Temple outside of a Phoenix
project with get some nice HTML functions as well as properly escaped
HTML out of the box.
This can be made optional if Temple becomes decoupled from the render
and it including HTML specific packages becomes a strange.
* feat: Allow user to make their own Component module
The component module is essentially to defer compiling functions that the
user might not need. The component, render_slot, and inner_block functions
are only mean to be used when there isn't another implementation.
In the case of a LiveView application, LiveView is providing the
component runtime implementation. This was causing some compile time
warnings for temple, because it was using the LiveView engine at compile
time (for Temple, not the user's application) and LiveView hadn't been
compiled or loaded.
So, now we defer this to the user to make their own module and import it
where necessary.
* feat: Pass dynamic attributes with the :rest! attribute
The :rest! attribute can be used to pass in a dynamic list of attributes
to be mixed into the static ones at runtime.
Since this cannot be properly escaped by any engine, we have to mark it
as safe and then allow the function to escape it for us. I decided to
leverage the `attributes_escape/1` function from `phoenix_html`. There
isn't really any point in making my own version of this or vendoring it.
Now you can also pass a variable as the attributes as well if you only
want to pass through attributes from a calling component.
The :rest! attribute also works with components, allowing you to pass
a dynamic list of args into them.
Fixes#183
* Move test components to their own file.
* docs(components): Update documentation on Temple.Components
* docs(guides): Mention attributes_escape/1 function in the guides
* chore(test): Move helper to it's own module
* feat: rest! support for slots
* docs(guides): Dynamic attributes
* ci: downgrade runs-on to support OTP 23
* Align component model with HEEx/Surface
This change aligns the component model with HEEx/Surface. This shoudl
allow one to interop components created in any syntax with any other
syntax.
The advantage of this is folks can utilize component packages created
using a different syntax.
This includes several enhancements and breaking changes, please see the changelog and the migration guide for further details.
Closes#130
slot definitions in a component instance can only exist in the root of
that component, with root being defined as the lexical scoping of the
slot still being the component it's defined in.
Fixes#126
Before this change, only keyword list literals could be passed to
elements. If they had non-literals as values, then those would compile
to EEx expressions.
This allows a non-literal to be passed as attrs and have the entire thing
compile to an EEx expression, which will pass the non-literal to a
"runtime_attrs" function, which evaluates a keyword list into a safe
string.
That last part might need to be reworked if the user is not using
the Phoenix.HTML.Engine EEx Engine.
* 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
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.
