This repository was archived by the owner on May 14, 2021. It is now read-only.
V2.1.0 specify fee #12
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nitzantomer
approved these changes
Mar 25, 2019
| } | ||
|
|
||
| public async send(operation: xdr.Operation<Operation>, memoText?: string): Promise<Server.TransactionRecord> { | ||
| public async send(operation: xdr.Operation<Operation>, options: { memo?: string, fee?: number } = {}): Promise<Server.TransactionRecord> { |
Contributor
There was a problem hiding this comment.
i see that this options type: { memo?: string, fee?: number } is used at least 3 times.
just extract it into a type:
type TransactionsOptions = { memo?: string, fee?: number; };
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
allow specifying fee
fix payment stream - to not keep sending the same transactions over and over