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
However, good responses don't have a status. This means that client apps can't write logic such as:
if aisResponse.status == 404:
// do something
since status doesn't always exist.
This should probably be consistent across all cases -- either by including a status on good responses, or by always sending back HTTP status codes in the headers. The former sounds more convenient.
The text was updated successfully, but these errors were encountered:
Error responses from the API have a
status
property, e.g.404
:However, good responses don't have a
status
. This means that client apps can't write logic such as:since
status
doesn't always exist.This should probably be consistent across all cases -- either by including a
status
on good responses, or by always sending back HTTP status codes in the headers. The former sounds more convenient.The text was updated successfully, but these errors were encountered: