[Feature request] Add more detailed error messages

[popojargo]

Expected Behavior

Display the Couch error message?

Current Behavior

If an error occurs, an error message is returned but it doesn't give us details.

Possible Solution

When we have an error message from Couch, perhaps we should return the error message.

I haven't thought a lot about this issue but I've seen a lot of people complain about (I even do) and I think it should be considered.

[Antonio-Maranhao]

Hey @popojargo I believe the real goal here should be better error messages. I agree 100% the generic Error doing_something is not helpful and goes against UX best practices. Having Something wrong. Reason:+<couchdb_msg> is relatively better (depending on the user) but it might not be ideal for all cases. CouchDB messages are sometimes not helpful either. Besides it's an API response, more for robots than humans.

To be clear, I'm not against your idea at all. I've done it myself because it's better than a generic message alone.

Ultimately we want the error messages to be helpful. Tell me why it didn't work and how can I fix it. I realize it's a bigger ask then what you're proposing here, and not easy/quick to implement, but I wanted to raise these points nevertheless.

There are some low hanging fruits though. For instance making the existing messages better by following a couple of guidelines:

• Avoid negative words: Oops, Error, Failed, Problem, Invalid, Wrong, Prohibited
• Avoid exclamation marks
• Don't blame the user
• If an error can be avoided (e.g. input validation) change the code to prevent it