fix: support optional params in ParsedArgs
types
#72
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.
π Linked issue
β Type of change
π Description
This PR allow the type
ParsedArgs
to support therequired
boolean property. Depending on the value of this property, theargs
coud betype | undefined
ortype
.positional
, If required is false, the type istype | undefined
. If required is false and a default value is provided, the type istype
. If required is true, the type istype
. If required does not exist, the type istype
.string
, If required is false, the type istype | undefined
. If required is false and a default value is provided, the type istype
. If required is true, the type istype
. If required does not exist, the type isundefined
.boolean
, If required is false, the type istype | undefined
. If required is false and a default value is provided, the type istype
. If required is true, the type istype
. If required does not exist, the type isundefined
.Improve DX.
Should I add some type tests?
π Checklist