fix: parse direct also inside init to make it work in programmatic usage #66
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.
To keep the same interface between the arguments passed through the cli, and the arguments passed throught the programmatic usage, the declaration of the init function define the direct arg as a boolean.
This is not entirerly true in the usage from the cli, since inside the parse function, the direct argument is converted to a number (0 or Infinite).
In order to make both the usages work with the same interface for the args, the PR adds an additional function in charge of preparing the arguments for being used in the core logic.
Specifically for this case, the direct argument is converted from a boolean to an integer as done in the setDefaults for the cli usage, only when it arrives from the init as true, or as someting differnt from a number.
fixes #35