-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
fix(predict): fix claim button not showing and not working for resolved positions #27050
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
Closed
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
557a442
fix: claim now works - was broken to incorrect wallet address look up
vinnyhoward 9e8a447
Merge branch 'main' of github.com:MetaMask/metamask-mobile into fix-t…
vinnyhoward 1e36186
fix: refactor lowercase sensitivity logic, simpflied fetching positio…
vinnyhoward 001152a
fix: reset has claim state
vinnyhoward e45d136
fix: refactor and update unit tests
vinnyhoward 9d40ff2
fix: unit test mocks
vinnyhoward File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,6 +12,7 @@ import { ensureError } from '../utils/predictErrorHandler'; | |
| import { usePredictTrading } from './usePredictTrading'; | ||
| import { ConfirmationLoader } from '../../../Views/confirmations/components/confirm/confirm-component'; | ||
| import Routes from '../../../../constants/navigation/Routes'; | ||
| import { PredictClaimStatus } from '../types'; | ||
|
|
||
| export const usePredictClaim = () => { | ||
| const { navigateToConfirmation } = useConfirmNavigation(); | ||
|
|
@@ -20,15 +21,22 @@ export const usePredictClaim = () => { | |
| const { toastRef } = useContext(ToastContext); | ||
| const navigation = useNavigation(); | ||
|
|
||
| const claim = useCallback(async () => { | ||
| const claim = useCallback(async (): Promise<{ | ||
| wasCancelled: boolean; | ||
| succeeded: boolean; | ||
| }> => { | ||
| try { | ||
| navigateToConfirmation({ | ||
| headerShown: false, | ||
| loader: ConfirmationLoader.PredictClaim, | ||
| // TODO: remove once navigation stack is fixed properly | ||
| stack: Routes.PREDICT.ROOT, | ||
| }); | ||
| await claimWinnings({}); | ||
| const result = await claimWinnings({}); | ||
| return { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We weren’t using the result before. Since we’re using it now, instead of returning flags, let’s return the result object itself so whoever consumes it can use it however they need. |
||
| wasCancelled: result?.status === PredictClaimStatus.CANCELLED, | ||
| succeeded: result?.status === PredictClaimStatus.PENDING, | ||
| }; | ||
| } catch (err) { | ||
| // Log error with claim context | ||
| Logger.error(ensureError(err), { | ||
|
|
@@ -70,6 +78,7 @@ export const usePredictClaim = () => { | |
| }, | ||
| }, | ||
| }); | ||
| return { wasCancelled: false, succeeded: false }; | ||
| } | ||
| }, [ | ||
| claimWinnings, | ||
|
|
||
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
We should not need this change. Also, we now use React Query for our positions queries and you should be reusing our hooks (or at least our queries) rather than creating custom fetch logic.
Let's have a sync on this if needed. We're happy to help fix the issues across the Predict section in the new homepage.