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
Typically when you issue a GET to grab a specific instance of something, as a developer, you want either the thing, or null, so you can do something like if(thing) doSomething(); afterwards.
Today if you get back a 404 from the server on an operation like GET /applications/{applicationName}, it will cause the promise to throw. Ideally this would instead resolve the promise with null.
The text was updated successfully, but these errors were encountered:
Typically when you issue a GET to grab a specific instance of something, as a developer, you want either the thing, or null, so you can do something like
if(thing) doSomething();
afterwards.Today if you get back a 404 from the server on an operation like
GET /applications/{applicationName}
, it will cause the promise to throw. Ideally this would instead resolve the promise withnull
.The text was updated successfully, but these errors were encountered: