But it would be nice to have the ability to have more than just the name variable in the template.
So:
import "{{package}}"
class {{name}} {
//things
foo({{myVariable}});
}
This could be done by checking the template for {{variables}}'s and then displaying them to the user to fill in in an output.
So the "thaum" UX could be updated to show:
$ thaum myTemplate
π Using thaum_files at: "/Users/Flaque/myProject/thaum_files"
name : <User has entered content here>
package : <User is prompted to enter content here>
myVariable : <User will be prompted for this after they complete the previous>
Pros
Requires 0 config files or complicated scripting (which is thaum's main reason for existing)
Subtly reminds the user which template by listing the variables.
Easy to use without needing to read docs.
Cons
Makes thaum a little more difficult to be used in conjunction with other scripts.
I'm personally okay with this as I don't see thaum as a tool that would be used like that. There are many other tools for generation in scripts out there and that's not really thaum's purpose.
But it would be nice to have the ability to have more than just the
name
variable in the template.So:
This could be done by checking the template for {{variables}}'s and then displaying them to the user to fill in in an output.
So the "thaum" UX could be updated to show:
Pros
Cons