-
Notifications
You must be signed in to change notification settings - Fork 983
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
Show correct error message when signing typed data #10328
Conversation
Hey @PascalPrecht, and thank you so much for making your first pull request in status-react! ❤️ Please help us make your experience better by filling out this brief questionnaire https://goo.gl/forms/uWqNcVpVz7OIopXg2 |
Pull Request Checklist
|
Since this is a fix, I assume it'd be good to add an e2e test as well? |
@PascalPrecht We don't add e2e for every fix (they are fairly slow to run as they run on a different platform on emulators), if you feel this needs testing you can add some tests in clojure (they are unit/integration tests). In case the feature needs e2e tests, generally is the test team that writes them and maintains them. |
Jenkins Builds
|
@cammellos fair enough! Thanks for letting me know! 🙏 |
Prior to this commit `sign-message-completed` effect would always use the `wrong-password` label for error handling. We now ensure that `wrong-password` is only used in case the error in question has a code `5`, which is associated to unmatching passwords. In any other case we'll use the `message` attached to the `error`. Fixes status-im#8275 Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
Prior to this commit
sign-message-completed
effect would always usethe
wrong-password
label for error handling. We now ensure thatwrong-password
is only used in case the error in question has a code
5
, which isassociated to unmatching passwords.
In any other case we'll use the
message
attached to theerror
.Fixes #8275