fix: Check if the wallet is connected and there's a current vault before showing toast #324
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Nice! Thanks for the quick turnaround :) |
Majorfi
approved these changes
Aug 14, 2023
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.
Description
Check if the wallet is connected and there's a current vault before showing toast
The assertion
currentVault?.chainID !== safeChainIDwastruebecause there wasn't acurrentVault, then when we went into that condition, we were defaulting to EthereumgetNetwork(currentVault.chainID || 1)which was causing the toast in the issue.Related Issue
Fixes #322
Motivation and Context
Show the warning correctly
How Has This Been Tested?
Locally, screenshot below
Screenshots (if appropriate):