Passing boolean flag options not working correctly #223
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the documentation it says you can disable various features by setting a flag to
false
. For example,--classic-decorator=false
will disable the insertion of the@classic
decorator.This doesn't work correctly because passing
--classic-decorator=false
actually gets transformed to{ classicDecorator: 'false' }
. TheclassicDecorator
value is actually a string value offalse
and therefore truthy.I originally opened this in the closed PR #212 but I revisited the approach.
I've introduced a change where we now use
yargs
parse the options into their correct types, i.e. Boolean and String. This means Booleans are now accurately represented.I haven't added a test but any suggestions on how to test this are welcome.
/cc @NullVoxPopuli @rwjblue