-
-
Notifications
You must be signed in to change notification settings - Fork 76
Conversation
So the basic functionality is always available, even without the `braintree_errors` partial.
Errors are not only used for hosted fields but also for Paypal, for example.
47c1a1c
to
18fed62
Compare
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 think we should just display the error message and don't prepend the default error, but display that if no other error message could be found.
var errorText = errors.join(", "); | ||
|
||
console.error("Error submitting transaction: " + errorText); | ||
SolidusPaypalBraintree.showError(BraintreeError.DEFAULT + " " + errorText); |
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.
A validation error is not "Bad", so we should not prepend all errors with the default message.
18fed62
to
20638da
Compare
@tvdeyen 👍 i agree. |
@alepore thanks. Build is failing because of rubocop. 😢 We really should not run rubocop on Travis CI, but use Hound for this. |
Add suggested puma dependency
aafc4b3
to
db63748
Compare
Use the driver provided by capybara.
db63748
to
273ca6f
Compare
@alepore one final rebase we are good to go. Thanks |
We currently don't display transaction errors on the checkout. This behaviour is very confusing for the user.
Even if the user may not be able to fix the error by itself, we should make clear that something bad happened.
This is the result:
