-
Notifications
You must be signed in to change notification settings - Fork 49
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
feature(wallet-mobile): new tx review for withdraw staking rewards #3707
feature(wallet-mobile): new tx review for withdraw staking rewards #3707
Conversation
@@ -152,6 +168,7 @@ type ReviewTxActions = { | |||
onErrorChanged: (onError: ReviewTxState['onError']) => void |
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 not a good idea to have objects that are not serializable in the state, (eg. if we decide to leverage persisted state this will fail), and context also can quickly become a problem
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.
Yeah. It is a temporal solution until the common error screens are implemented
@banklesss bring it in, but create a task to remove all callbacks out of the state. |
Description / Change(s) / Related issue(s)
New tx review for withdraw staking rewards feature.
Includes a operations refactor.
Ticket
YV-41