* 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
This basically just adds svg elements as void and nonvoid element
aliases and it works, will test on a real proejct before releasing the
next release.
Also, fixed the weird behaviour problem by defining types for each of the ast
nodes and then referencing those types when defining the ast type.
Unclear why this works, but I imagine it has to do with the types not
being a big part of the compilation process or something.
This also uses the typed_struct library to do so. Seems pretty slick and
does what it claims it does.
* Fine tune whitespace
The EEx outut now emits more human-readable and predictable formatting.
This includes proper indenting, at least for each "root" template.
* Internal whitespace control
You can now use a bang version of any nonvoid tag to emit the markup
witout the internal whitespace. This means that there will not be a
newline emitted after the opening tag and before the closing tag.
Integration test for slots
Format integration test project
Hide slots assign in temple prefixed key
Won't compile temple related assigns when calling Utils.runtime_attrs
Update component docs with slots usage
* 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
