Mandatory answer and weird behavior with no default value

[ppo]

trafficstars

The documentation says: default: Leave empty to force the user to answer.

When not specifying the default key, the default value is None; perfect.
But the prompt shows 🎤 [None]:.
I think it should be 🎤 : maybe with above that VAR_NAME? Required. Format: str

When pressing enter, it should not accept an empty answer and should ask again (i.e. force the user to enter a value… as mandatory, and as described in the doc)

Currently, if pressing enter, that variable is None and using it in another default value "as a string", if becomes the string"None"… which is a known "problem" with Jinja (or Django templates at least).
Wouldn't it be better to use an empty string "" rather than None (for str variables)?

[drts01]

FWIW I think an empty str would be good, in the event that is what the user wants to allow. If an empty str is not valid, in v6.1 the validation will handle that (#398).

[eyllanesc]

I think that the "default" field should not be used to indicate that the answer is required, a field called "required" or "mandatory" should be created, if the "default" field is used then it is equivalent to required=false but an empty string in the default field should not imply required=true since in some cases the default value may be an empty string. Also the "required" field should be true by default.

And if the "validator" field is implemented then it should work together with that field.

[csadorf]

This issue is leading to very confusing questionnaire behavior. Would it be possible to up the priority? Especially because it is user-facing?

[yajo]

We have validators now in 6.2. Have you tried with those?

[csadorf]

We have validators now in 6.2. Have you tried with those?

I had not, thank you for pointing this out. This does constitute a viable work-around for the problem.