Input validation for names

[kittauri]

Check the input for permitted designations for the names. At the moment this is only checked at the end. This means that if someone does not know what is allowed to be entered, they go through all the settings, only to be told at the end that they can start from the beginning.

Not all people are aware of all the naming conventions. CLI should be more robust against user behavior.

[davisagli]

This would be better UX, but as far as I am aware, cookiecutter (which we use for the prompts) doesn't provide a way to validate options one at a time while they are entered. @ericof Is that right?

[stevepiercy]

Validation for each input is possible for only a few limited options, including booleans and option lists. See example below.

You've downloaded /Users/stevepiercy/.cookiecutters/cookieplone-templates before. Is it okay to delete and re-download it? [y/n] (y): x
Please enter Y or N

Input validation is one of the most wanted and longest requested features, going back to 2015. But it's a huge amount of work, some of which has been done in forks and is being slowly integrated. See:

• New cookiecutter.json format and more for cookiecutter 2.0 cookiecutter/cookiecutter#1567

[stevepiercy]

Side note, I think that Cookiecutter maintainers should seek fiscal sponsorship from the Plone Foundation, the Python Software Foundation, or any other organization that is willing to provide the bank account to receive and disburse funds to support its development.

[ericof]

I'm in contact with Audrey about the future of cookiecutter. Let's see how it evolves

[tkimnguyen]

Related discussion by someone who ran into this issue:

https://community.plone.org/t/cookieplone-and-is-not-a-valid-python-identifier/22674?u=tkimnguyen