feat: check for ibc timeout if a response was not provided by the chain #1592
Conversation
This file contains 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
pedrorezende
force-pushed
the
namadillo/ibc-fixes-improvements
branch
from
949f359 to
f6fa903
Compare
euharrison
approved these changes
Jan 31, 2025
| timeoutHash = timeoutQuery[0]?.hash || ""; | ||
| } | ||
|
|
||
| return [isTimeout, timeoutHash]; |
There was a problem hiding this comment.
I'm thinking if we should use object on these cases. The array tuple is great for useState because it's a well know function and we rename the returned values. But, on other functions, it's harder to read and understanding the code, also, usually we don't rename the value, actually, we use the same name
const [isTimeout, timeoutHash] = await checkForIbcTransferTimeout(client, tx);
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.