-
Notifications
You must be signed in to change notification settings - Fork 4
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
Map error type to message #1782
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -63,9 +63,10 @@ const WalletSelect = () => { | |||
)} | |||
{hasError && ( | |||
<div className="text-vermilion ml-auto text-ztg-12-120 w-ztg-275"> | |||
{error.type === "NoAccounts" |
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.
What does this actually change? Since error type should only be one of two types it seems like the old code should cover all cases?
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.
I suspect the types are probably wrong and not all errors are accounted for. Even so, I don't think the previous code is good practice as it assumes that there will only ever be 2 error types
closes #1763