enhancement: Change signature of ClientOption.signTransaction to be able to pass KeyPair #1063 #1127
+44
−7
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.
Change signature of ClientOption.signTransaction to be able to pass KeyPair #1063
Closes #1063
Pull Request Description
Summary
This pull request modifies the
ClientOptions
type to allow thesignTransaction
property to accept aKeypair
in addition to a function. This change simplifies the process of signing transactions, especially for testing and simple applications, by allowing users to directly use aKeypair
without needing to implement a custom signing function.Changes Made
signTransaction
property to accept either aSignTransaction
function or aKeypair
.sign
method to handle the case wheresignTransaction
is aKeypair
.Keypair
is provided, it uses thebasicNodeSigner
to create a signing function.