-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix(background): better error message for connectWallet
#396
Conversation
connectWallet
Extension builds preview
|
@@ -23,5 +23,8 @@ | |||
}, | |||
"siteNotMonetized": { | |||
"message": "This website is not monetized." | |||
}, | |||
"error_connectWallet_invalidClient": { |
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.
Looking into this convention for future:
error_*
for error messagesaction_*
for button/link actionsstate_*
mostly everything else- and rest can be anything I guess?
Can't use /
or .
or :
unfortunately.
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 would suggest error_openPayments_invalidClient
for this.
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 was not going for openPayments here as this error is specific to one we show during connect wallet. When it happens during payment (openPayments_invalidClient again), we go for "key revoked" state which has its own error messages. We might show a different one during reconnectWallet even.
4ca8a3d
to
0585d57
Compare
@@ -23,5 +23,8 @@ | |||
}, | |||
"siteNotMonetized": { | |||
"message": "This website is not monetized." | |||
}, | |||
"error_connectWallet_invalidClient": { |
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 would suggest error_openPayments_invalidClient
for this.
Co-authored-by: Radu-Cristian Popa <[email protected]>
Context
Part of #147
Changes proposed in this pull request