From 01bce6bdec31c9db9b17afde13d2ca60d1a81a31 Mon Sep 17 00:00:00 2001 From: JesseBrault0709 <62299747+JesseBrault0709@users.noreply.github.com> Date: Fri, 17 May 2024 15:04:16 +0200 Subject: [PATCH] Updated TODO. --- web-views/todo.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/web-views/todo.md b/web-views/todo.md index b590584..8834442 100644 --- a/web-views/todo.md +++ b/web-views/todo.md @@ -10,8 +10,17 @@ 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. - [ ] 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. + - 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 - Perhaps we could have a lambda- or closure-like factory at the beginning of a component for creating it. This could