Bug: CLI does not handle options with value of zero correctly #1421
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.
The CLI option parsing code did a truthy test to determine whether a user provided a value for an option. This meant that values of 0 were being ignored. This is an issue in particular for serverless-autoprune-plugin:
arabold/serverless-autoprune-plugin#3
This PR fixes the bug by doing an explicit null/undefined check instead.