APIs, we have a Problem JSON
When designing a web API, not only do you have to think about the happy path when everything is alright, but you also have to handle all the error cases: Is the payload received correct? Is there a…
Read the full articleYou might also wanna read
ProblemDetails in ASP.NET Core – Standardizing API Error Responses
Learn how to use ProblemDetails in ASP.NET Core to standardize error responses in your Web APIs. Understand default behavior, customization,
Challenges of Asynchronous Error Handling in API Design
Or, How I Learned To Stop Worrying And Deprecate cudaGetLastError()
parallelprogrammer.substack.com·1y agoElevated errors for Responses API
Status: Resolved All impacted services have now fully recovered. Between 4:05pm and 4:40pm PT on May 8, some customers using the Responses A
Addressing Flaws in Ruby's JSON Gem API
As I mentioned at the start of my Optimizing Ruby’s JSON series of posts, performance isn’t why I candidated to be the new gem’s maintainer.
byroot.github.io·11mo ago
Writing Robust Code: Reducing Assumptions and Handling Real-World Imperfections
We can all write elegant scripts, that assume a lot. And assumption is the mother of all ...
ryelang.org·4d agoUnderstanding HTTP Status Codes – Returning Proper API Responses in ASP.NET Core
Master HTTP status codes for your ASP.NET Core Web APIs. Learn when to use 200, 201, 204, 400, 401, 403, 404, 409, 422, 500, and more - with
Comments
Sign in to join the conversation.
No comments yet. Be the first.