-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExecuteSwapRequest improvements #734
Labels
Milestone
Comments
@kilrau Did you mean I should add this to the |
yep |
I think that this will be effectively resolved by #787, which distinguishes between swap successes and failures by naming the fields |
sangaman
added a commit
that referenced
this issue
Jan 22, 2019
This adds a `SwapFailure` message type to the asynchronous `PlaceOrder` rpc call. It is used to notify the caller in real time when a swap fails for a given order. This also renames `SwapResult` to `SwapSuccess` to clearly distinguish it from the unsuccessful `SwapFailure`. Closes #609. Closes #734.
Ok, good to close this one then. Naturally you'll get rewarded for your work nevertheless @ImmanuelSegol |
sangaman
added a commit
that referenced
this issue
Jan 23, 2019
This adds a `SwapFailure` message type to the asynchronous `PlaceOrder` rpc call. It is used to notify the caller in real time when a swap fails for a given order. This also renames `SwapResult` to `SwapSuccess` to clearly distinguish it from the unsuccessful `SwapFailure`. Closes #609. Closes #734.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
add
result: completed
/failed
. This won't necessarily be used programmatically in the end, but makes the situation much clearer for engineers integrating & testingxud
. Feedback from our test integration.The text was updated successfully, but these errors were encountered: