feat: add dynamicTypes option to use function when looking up types #125
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.
Note: this is stacked on #124 since it had some potential conflicts. That one should land first.
This PR adds an option named
dynamicTypes
to go along with the existingtypes
option.Currently,
nopt
looks up each potentialkey
in thetypes
object. Iftypes
doesn't have a property by that name, then the current fallback is to parse it as a boolean and leave the value inargv.remain
.With
dynamicTypes
, you can specify a function that will receive each unknown key and can either return a type orundefined
to keep the current behavior.Here's an example: