jessebrault/groowt
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated TODO.

Browse Source
This commit is contained in:
JesseBrault0709 2024-05-17 15:04:16 +02:00
parent 87f2ae6d93
commit 01bce6bdec
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
web-views/todo.md
View File

@ -10,8 +10,17 @@
for differentiating between closures/scriplets that take an `out` (left-shiftable) param and ones that don't take any. for differentiating between closures/scriplets that take an `out` (left-shiftable) param and ones that don't take any.
- This could also make differentiating lazy/eager closures/scriptlets easier. - 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 support `data-`, etc. - [ ] Check that the lexer/parser can handle `-` dashes in component names/types, so that we can support `data-`, etc.
- [ ] Think more about how to compile templates and components alongside each other. Perhaps we just need to bite - [X] 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 `CompilationUnit` or `CompilerConfiguration` or whatnot to identify `.wvc` files. the bullet and use a custom Groovy `CompilationUnit` or `CompilerConfiguration` or whatnot to identify `.wvc` files.
- Update 5/17/24: This should be solved with the `DelegatingWvcParserPlugin` which just examines the file extension.
- [ ] Get rid of automatically generated script `main` and `run` methods; replace with a custom `main` method which
forwards the args to a helper class and then runs the template with the variables similar to the current `runTemplate`
helper tool.
- [ ] Create a custom tool for compiling which simply forwards to the Groovy `FileSystemCompiler` but with the correct
compiler configuration and parser plugin factory.
- [ ] Create smoke screen test cases for the compiler.
- [ ] Separate the api, runtime, and compiler elements. The api/runtime can depend on the compiler. If users really want
to meddle with the compiler for some reason, they can depend on it directly.
## Syntax ideas ## Syntax ideas
- Perhaps we could have a lambda- or closure-like factory at the beginning of a component for creating it. This could - Perhaps we could have a lambda- or closure-like factory at the beginning of a component for creating it. This could