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
for get, post, put, ... without convertResponseToObject no HTTP status (including 4xx and 5xx) would be treated as an error.
for getResource and get, post, put, ... with convertResponseToObject HTTP status outside of 200 - 299 (in particular 4xx and 5xx) would be treated as an error.
I'm not sure if it is a good idea to change the semantics of "error" and therefore error handling code depending on a configuration option. It has a certain smell to it.
The text was updated successfully, but these errors were encountered:
basti1302
changed the title
Should HTTP status codes be treated differently when convertResponseToObject is enabled
[discussion] Should HTTP status codes be treated differently when convertResponseToObject is enabled
Feb 1, 2016
For example:
See also traverson/traverson-angular#14.
I'm not sure if it is a good idea to change the semantics of "error" and therefore error handling code depending on a configuration option. It has a certain smell to it.
The text was updated successfully, but these errors were encountered: