-
Notifications
You must be signed in to change notification settings - Fork 1
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
Pedro/cow 284 milestone review 2 #707
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
value={{ | ||
managedTransaction, | ||
}} |
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.
any reason why encapsulate this in another object?
}, [isPonderAPIUpToDate]); | ||
|
||
useEffect(() => { | ||
if (!["final", "confirmed", "error", "idle"].includes(status || "")) { |
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 remove confirmed
from this now right?
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're using more the ponder update as a trigger, so I think that is ok to let this
!["final", "idle", "confirmed", "error"].includes(status || "") | ||
} | ||
loadingText="Depositing..." | ||
loading={isSubmitting || isAmmUpdating} |
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.
so are we ignoring the tx now 🤔 ?
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.
actually the isAmmUpdating
is true
when the status is something being processed.
No description provided.