By far not the cleanest implementation, if you think this or someone like this makes sense, this would probably need to be partly refactored.

This is more of a quickly thrown together aproach to having some form of global values.

I first thought of global values set for all templates, but that would easily clash because multiple templates could use the same key for different use cases.

(My usecase is e.g. the GitHub account/org).

1. valid_ident
2. crate-name
3. sem.ver (I don't have any use for that one, just came to mind)
4. a verifying pattern (regex?)

Maybe I will look into implementing this myself

Not sure if this is something that should be done in tera, but we could also just add these our selves.

Specifically, I'd like a file_name filter to get the name of the path in project_name

Also, the name project_name is a bit confusing as it actually just is the relative/absolute path, that often ends up just being a dir name.

add a condition similarly to the file ignores to arguments to allow only querying some options when an earlier prompt was answered with yes.

[bin_install]
type = "bool"
description = "Enable binary installer (requires releases on GitHub)"
default = true

[github_repo]
type = "string"
description = "Enable binary installer (requires releases on GitHub)"
condition = "{{ bin_install }}"

should only ask for github_repo if bin_install is answered with yes.

Some improvements I thought of, feel free to filter/change

• fix: only check is empty on existing dirs
• fix: allow omitting ignore in repo settings
• feat: allow using a single path directly as a string in ignores

I just created the project in my parent directory by accident.

I think there is a reason many tools only allow using an existing directory if it is empty.

Maybe a compromise could be to either ask "Are you sure you want to hatch in this non empty directory direcotry_name?" or require passing the current directory as . .

I hope I don't anoy you too much with these issues. It's a great tool, and I really enjoy using it.

This supports excluding files from being executed as a template but keeps them arround to be used by templates.

This allows both files containing invalid templates without wrapping them in {% raw %}, but more importantly it allows macros.

The problem with macros is, that they are not allowed in templates, so this is the only way to implement them.

files with template = false are now added to template_files so they can be referenced, but they are not rendered as templates them selves.

closes #14 somewhat resolves #9

I created a base template containing some boilerplate for my github workflow files.

I'd like to use it for generating, but exclude it from the output. https://tera.netlify.app/docs/#base-template

I cannot add it to .hatchignore because then it will not be present for the template generation.

My Idea would be to have it run with the context of already specified arguments (Hopefully we find a good way to do this in #8).

• if it evaluates to only whitespace the value is valid
• else the result is printed as error message

We discussed this earlier, but I have a few ideas that should make this viable:

1. from from either a tag e.g. "0.1" or from a commit sha 0c4a3.
2. Modes for cleaning up files generated by from version a. force-clean: Delete all files that were created by from version b. try-clean: Check if any files created by from version were changed, if yes fail. c. partial-clean: Only delete all the files that were not changed
3. Modes for generating new files a. force-gen: Replace existing files with newly generated ones b. try-gen: Fail if any files would be overwritten c. partial-gen: Only generate files that would not overwrite existing ones.
4. Have combined modes, i.e. force, try, partial
5. For values: a. have some form of input file b. just respecify all the values, as they might have changed from version to version as well.

With a vc project you can just use force and than have a look at the diff.

Same behavior as with defaults (using json for encoding of list and multi_list).

My usecase:

First question selects a set of features.

Second question selects one of them as default: should only offer the ones selected in question 1.

I have a file using terra like templates inside a template.

So having the ability to change the delimter to some other character would be great.

Related tera issue: https://github.com/Keats/tera/issues/343