Skip to content
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

Feat(XLM memo exchanges) #1584

Merged
merged 3 commits into from
May 6, 2019
Merged

Feat(XLM memo exchanges) #1584

merged 3 commits into from
May 6, 2019

Conversation

schnogz
Copy link
Contributor

@schnogz schnogz commented May 2, 2019

Description

  • Warns users to add memo if they are sending XLM to an exchange.

Change Type

  • Feature

Testing Steps

Detail the steps required for the reviewer(s) to verify and test these changes.

Code Checklist

  • Code compiles successfully (verified via yarn start)
  • README.md and other documentation is updated as needed

@@ -91,8 +91,10 @@ export default ({ api, coreSagas }) => {
payment = yield payment.to(value)
// Do not block payment update when to is changed w/ destinationAccount check
yield put(A.paymentUpdatedSuccess(payment.value()))
// After updating payment success check if destinationAccount exists
// check if destination exists
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This specifically needs to happen after updating payment success. If thats clear enough then fine to remove

yield put(A.sendXlmCheckIfDestinationIsExchangeFailure(e))
}
}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no latency in this check so it should not follow Remote paradigm imo

@plondon plondon merged commit 9a88d0b into development May 6, 2019
@plondon plondon deleted the feat/xlm-memo-exchanges branch May 6, 2019 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants