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
ExceptionRenderer prints out t.message and t.cause properties but I have come across a few endpoints that put the meat of their error message in a property called t.content.
Debugging chores would benefit greatly and take a lot less time if t.content were added to all of ExceptionRenderer's output.
The text was updated successfully, but these errors were encountered:
Colin -- is it fair to say you are talking about this exception that we generate here in JsonClient? That you should think it should be serialized with the content, if appropriate? To be clear this is specific to REST and HTTP exceptions.
So colin and I looked at this -- this is just a particular property that is surfaced in a client-specific HttpException. So the ticket is a bit more tricky that the title implies.
But the general goal is good. Perhaps JSONClient should extract useful information from the "content" of the return into the frameworks ExternalHttpException. This could perhaps be partially elevated into the message, or at least made available
in the JSONFormat.
lbwexler
changed the title
Add content to list of properties printed by ExceptionRenderer
Enhance ExternalHttpException to provide information from content.
Aug 19, 2022
ExceptionRenderer
prints outt.message
andt.cause
properties but I have come across a few endpoints that put the meat of their error message in a property calledt.content
.Debugging chores would benefit greatly and take a lot less time if
t.content
were added to all ofExceptionRenderer
's output.The text was updated successfully, but these errors were encountered: