1.6 KiB
1.6 KiB
TODO and general notes
TODO
- Think about syntax for scriptlets. What semantic differences o we want between
${},<%= %>, and<% %>. - Can the DollarScriptlet instead not include the dollar, more like React?
- Think about namespaces. This could ease having to write imports, because the namespace would automatically be
mapped to a star import. Syntax could be something like
<turbo::Frame someKey='someVal' />. - Think about how GString are currently done. Do we need to even parse them as such, between element/component tags?
Could we instead just have the
writervariable take individual values? This would simplify implementation logic for differentiating between closures/scriplets that take anout(left-shiftable) param and ones that don't take any.- This could also make differentiating lazy/eager closures/scriptlets easier.
- Check that the lexer/parser can handle
-dashes in component names/types, so that we can supportdata-, etc. - Think more about how to compile templates and components alongside each other. Perhaps we just need to bite
the bullet and use a custom Groovy
CompilationUnitorCompilerConfigurationor whatnot to identify.wvcfiles.
Syntax ideas
- Perhaps we could have a lambda- or closure-like factory at the beginning of a component for creating it. This could
bypass the resolve mechanism and just instantiate the component directly via constructor (with some protocol).
Something like:
<Component::new ...>or<Component.&new ...>. Could also have<{ new Component() } />.