-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support isAllowEmpty
in multi-select prompt
#42
Support isAllowEmpty
in multi-select prompt
#42
Conversation
🦋 Changeset detectedLatest commit: 45ceace The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! I think required
would be a better name for this, do you mind updating the PR?
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
Check operation 👀
Kapture.2023-02-17.at.12.10.48.mp4
Kapture.2023-02-17.at.12.11.42.mp4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks for the updates!
close #41
It would be a little more flexible if we could use empty arrays in the multi-select prompt.
First, I think simply be used as an option (any thoughts are welcome)