-
Notifications
You must be signed in to change notification settings - Fork 61
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
Expose "jse_shortmsg" publicly #70
Comments
The conclusion in #52 was to use the |
@davepacheco Sorry I should have mentioned this. Yes, I did look at #52. The problem with using The solution I was looking for is to provide a way to get both the chained long error message and the short version as well. It seems that with |
Thanks for clarifying. I haven't thought about it much but it seems like we could add a method to WError to get the long message. I prefer that slightly to adding a short message to VError but either may be okay. |
No problem, thanks so much for all the hard work, this is an amazing library! I would prefer just adding it to |
This is exactly the same request as the #52.
The use case is that I want to capture the entire error with all the causes for debugging, logging and other purposes. But when I return the JSON back to the client. I only want the user to see what is in the "jse_shortmsg".
For example:
The text was updated successfully, but these errors were encountered: