Should we optimize cookiecutter.XYZ == "y"?

I think we should move from this pattern:

{% cookiecutter.XYZ == "y" %}

to this pattern:

{% cookiecutter.XYZ.lower() in ["y", "yes"] %}

Thoughts?

[hackebrot]

Hi there! 👋

Ideally we would move to a new context format which supports typed Cookiecutter variables.

Doing so would allow us to better separate the UI from the template code, meaning that as a template author I would not have to care about accepted input values for variables, but only about the value that Cookiecutter writes to the context for that particular type.

For instance ["y", "ye", "yes"] might be all valid values for a Boolean variable, but will be stored as True in the Cookiecutter context resulting in the following template code:

{% if cookiecutter.XYZ %}
Hello {{ cookiecutter.name }}!
{% endif %}

I believe one of the reasons for Cookiecutter’s popularity and adoption in the Python community is that it uses the Jinja2 template engine and folks don’t have to learn yet another template language. So I’d prefer to not introduce any Cookiecutter specific APIs to templates.

[github-actions[bot]]

Automatically closing after waiting for additional info. To re-open, please provide the additional information requested.