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
Every API is different about how it throws back errors. It's quite important that we show a useful message to the user, rather than "Bad request" or "Invalid status code".
We need a JS function on the global level which automatically tries to pull out errors from the body on failure.
The text was updated successfully, but these errors were encountered:
Maybe this could/should simply be encompassed in the afterFailure, as you say. Here's an example. If you try to create a Salesforce lead with invalid date, you'll get this:
But the actual error is this:
It just feels like we could do more to easily surface that error info on the top level, if it exists. Maybe we just need more effort on the part of the connector developer rather than a falafel implementation.
Every API is different about how it throws back errors. It's quite important that we show a useful message to the user, rather than "Bad request" or "Invalid status code".
We need a JS function on the global level which automatically tries to pull out errors from the body on failure.
The text was updated successfully, but these errors were encountered: