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
Has any consideration been given to supporting RFC 9457 (Problem Details for HTTP APIs)?
For example, some of the defined members in the response could be added to the error raised by raise_for_status(). Currently, if I get a 422, I log the error, but all I get is "422 Unprocessable Entity", but the detail I really want is in the detail member of the response object.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Has any consideration been given to supporting RFC 9457 (Problem Details for HTTP APIs)?
For example, some of the defined members in the response could be added to the error raised by
raise_for_status()
. Currently, if I get a 422, I log the error, but all I get is "422 Unprocessable Entity", but the detail I really want is in thedetail
member of the response object.Beta Was this translation helpful? Give feedback.
All reactions