-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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(ramp): add sell fields to order details view #7742
Conversation
…l-transaction-hash
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2a856aeb-942a-4879-b059-2b160cb1ac6a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments
app/components/UI/Ramp/common/Views/OrderDetails/OrderDetails.tsx
Outdated
Show resolved
Hide resolved
const handleMakeAnotherPurchase = useCallback(() => { | ||
navigation.goBack(); | ||
navigation.navigate(Routes.RAMP.BUY); | ||
}, [navigation]); | ||
navigation.navigate( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the UI respond the same way if you remove navigation.goBack
or do both pages live on the same stack?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are not on the same stack, the back dismisses the current order details and then the navigate opens the Buy or Sell flow.
<ErrorView | ||
description={error} | ||
ctaOnPress={handleOnRefresh} | ||
location="Order Details Screen" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a constants file that we can put this in?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes this is already a type, if you input anything different than what's defined it will error (location type mismatch). https://github.com/MetaMask/metamask-mobile/blob/feat/ramp-sell-order-details/app/components/UI/Ramp/common/types/analytics.ts#L1-L12
63a00d0
to
abba5fc
Compare
@Cal-L this is ready for your re-review. I have responded to your comments. Since your last review we have:
|
12a7983
to
59868b1
Compare
@Cal-L any further comments/changes will be addressed in a new PR |
Kudos, SonarCloud Quality Gate passed! |
@georgeweiler LGTM I verified the order details view ✅ |
Sounds good! |
Description
Adds support on the order details page for sell orders.
Related issues
N/A This is a new feature
Manual testing steps
Add a sell order to your app state and check the order details page
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist