refactor(main)!: moves optional parameters to the options - BREAKING #44
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.
Description
pOldRevision
andpNewRevision
parameters from the main functionoldRevision
andnewRevision
attributes to the options object passed to the main function that have the same function as the removed parameters.Motivation and Context
This makes the interface less klunky to use - the parameters were both optional and either one could be passed, which would result in calls with the parameters that aren't relevant in the context as
null
likemain(null, "somebranch")
ormain("develop", null {trackedOnly: true})
.How Has This Been Tested?
Types of changes
Checklist
📖
⚖️