You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if a user has Solidus::TaxCloud installed and checks out with a bad zip code - namely a zip code that does not exist in that US state, for instance 19130 in Rhode Island - the checkout flow will fail with an exception.
Ideally we should simply halt the checkout at the current step and display a error message attached to the form.
Is there a best practice for how to rescue TaxCloud::Errors::ApiError and return its error message attached to the address input form?
I know that in ActiveMerchant there is a pattern like
Currently if a user has Solidus::TaxCloud installed and checks out with a bad zip code - namely a zip code that does not exist in that US state, for instance 19130 in Rhode Island - the checkout flow will fail with an exception.
Ideally we should simply halt the checkout at the current step and display a error message attached to the form.
Is there a best practice for how to rescue
TaxCloud::Errors::ApiError
and return its error message attached to the address input form?I know that in ActiveMerchant there is a pattern like
Is is possible to do something similar here but with the billing and shipping address step, rather than the payment step?
The text was updated successfully, but these errors were encountered: