fix: corrected optional parameter type #144
Closed
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.
Changes
Please describe both what is changing and why this is important. Include:
Summary
In the types for the verify method there is an optional param
requestedNonce
with no default value which is followed by a required parametercb
. This throws an error with tscTS1016
and is preventing my team from fixing an issue with an alternative package (we decided to use this one to replace it).To fix this issue I've changed the
requestedNonce
parameter to be of typestring | undefined
and made it a required parameter. However I'm not entirely sure if this is the correct solution and perhaps (after look at your codebase) you're looking for requestedNonce or callback which would require 2 different declarations shown below.Alternative declarations
Based on the codebase I think this is possibly what you're after
The above then allows requestedNonceOrCb or be either string or verifyCallback and depending on those types (if string) then the cb param is required else is not
References
Please include relevant links supporting this change such as a:
Testing
Please describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.
Checklist