If you're developing an HTTP API, having a consistent way of returning errors can make handling errors on the client-side simpler.
I've talked about Problem Details in another video, which is a standard for returning machine-readable details of errors in an HTTP Response. In this video, I'll cover how to consume those errors from the client-side.
Dotnetos Essentials is a new, free online course that provides you the basics (and some advanced topics) of async programming and concurrency, C# 9.0 and .NET diagnostics. 3 online courses gathered in one place for you to enjoy! Sign up on our website for 1 month free access to Async Expert, .NET Diagnostics Expert and C# 9.0 Professional.
https://essentials.dotnetos.org/?utm_...
🔔 Subscribe: / @codeopinion
💥 Join this channel to get access to source code & demos!
/ @codeopinion
🔥 Don't have the JOIN button? Support me on Patreon!
/ codeopinion
📝 Blog: https://codeopinion.com
👋 Twitter: / codeopinion
✨ LinkedIn: / dcomartin
TypeScript Problem Details Parser
https://github.com/PDMLab/http-proble...
0:00 Intro
0:57 Problem Details (RFC7807)
3:10 Client
6:15 Type & Extensions
#httpapi #softwarearchitecture #softwaredesign
In questa pagina del sito puoi guardare il video online Handling HTTP API Errors with Problem Details della durata di ore minuti seconda in buona qualità , che l'utente ha caricato CodeOpinion 29 settembre 2021, condividi il link con amici e conoscenti, su youtube questo video è già stato visto 17,399 volte e gli è piaciuto 439 spettatori. Buona visione!