Allow null text option #3
Conversation
There was a problem hiding this comment.
hey @bobbwhy, thanks for the pull request!
i appreciate you documenting the proposed feature in detail, as we can eventually re-use the proposal to be documentation for the new feature.
gave some feedback.
| Currently, the cli prompter will not accept a null string as the entered | ||
| value, but will instead simply repeat the prompt. | ||
|
|
||
| This proposal would add an option, **allowNull** to each question object |
There was a problem hiding this comment.
what about required? would that support the same use case?
| @@ -0,0 +1,4081 @@ | |||
| { | |||
There was a problem hiding this comment.
i'm not sure about committing package-lock.json or yarn.lock for a library repo, it adds git bloat and doesn't really provide any benefit when libraries are developed sparingly and you want the dependencies to match what a new user would experience (not what's in your lock file). thoughts?
There was a problem hiding this comment.
👍 Although I can see the value of a lock file in a company shipping a customer-facing app, I don't think it is necessary for libraries and their dependencies.
This proposal would add an option, allowNull to each question object
passed into a prompt.