It seems 37ccb64eacc636182ca4daa972bbc1ad56bc38a8 introduced a little bug where the following:
opt = Option.String(`--foo`, `bar`);
Caused opt to be inferred as string | boolean. I believe this is due to the tolerateBoolean options being incorrectly set as optional in their alternatives, when they should instead be required (since otherwise TS will interpret the lack of options as tolerating boolean, which isn't the intended default behaviour).
I also fixed the interaction of tolerateBoolean w/ validators, since the validators probably shouldn't run on those values.
It seems 37ccb64eacc636182ca4daa972bbc1ad56bc38a8 introduced a little bug where the following:
Caused
optto be inferred asstring | boolean. I believe this is due to thetolerateBooleanoptions being incorrectly set as optional in their alternatives, when they should instead be required (since otherwise TS will interpret the lack of options as tolerating boolean, which isn't the intended default behaviour).I also fixed the interaction of
tolerateBooleanw/ validators, since the validators probably shouldn't run on those values.cc @paul-soporan