`allowed` incompatible with `required: false` about bashly

[DannyBen]

Excellent. Thanks for confirming. I will release tomorrow.

[DannyBen]

Well, this is by design.

Setting the allowed whitelist, means the variable you receive in your script will always only be one of the allowed options - so it either needs to be required, or have a default value, or provided by the user.

The docs are not wrong in stating it can be used with either default or required. There is no need to ever specify required: false, only required: true since false is the default.

In your use case, allowing the --exclude flag to receive a none value, is the way to solve this.
The user does not need to specify --exclude none, since you make it the default.

name: download
help: Sample minimal application without commands
version: 0.1.0

args:
- name: source
  help: URL to download from
  default: sphinx
  allowed: [sphinx, abc, wonder]

flags:
- long: --exclude
  short: -e
  arg: action
  help: Avoid executing this action
  default: none
  allowed: [a, b, c, none]

You can see all the combinations of allowed and required/default in the whitelist example.

I will look into it a little deeper, to see if there is a path to modifying this behavior without opening a can of worms.

[DannyBen]

Well - I am not happy with what I just did....
Your comment about repeatable that makes it work as expected makes your point more obvious.

I will attempt to make it work as you expect.

[DannyBen]

This is fixed in the master branch. Can you review and/or test that it matches your expectation?
You can run the unreleased version using one of these ways.

[ChipS3t]

I can confirm this now works as expected.

If the flag or arg sections of the bashly.yml file contain an allowed option and required: true is not set, the argument or flag is optional as expected and will no longer throw an error if a value is not provided on the command line without the need for the default option.

[DannyBen]

Version 1.0.3 was released, including this fix.