2 best practices for returning api errors in asp.net core
Published 5 months ago • 21K plays • Length 12:39Download video MP4
Download video MP3
Similar videos
-
13:06
get rid of exceptions in your code with the result pattern
-
13:41
the new global error handling in asp.net core 8
-
0:25
multiple ef query filters? it can't be done ❌
-
0:18
how do you deprecate an old api version in asp.net core?
-
16:09
the brand new way to do fault handling in polly v8
-
6:48
sprint qualifying highlights | 2024 austrian grand prix
-
24:50
figma 3.0 (dev mode, ai, slides and more)
-
18:09
the best way to implement long running tasks in .net - hangfire, blazor, signalr
-
12:55
the best .net rest api client you didn't know about
-
0:17
did you try the new iexceptionhandler in asp.net core 8?
-
10:58
make your asp.net core api controllers incredibly simple
-
16:10
repr (request-endpoint-response) pattern will make your apis clean
-
5:46
handling http / api errors in power query | return api errors instead of power query default ones
-
19:24
completely get rid of exceptions using this technique
-
8:56
handling http api errors with problem details
-
4:26
rabbit r1 makes catastrophic rookie programming mistake
-
14:56
fix your controllers by refactoring to minimal apis
-
0:35
repr (request-endpoint-response) pattern and apiendpoints
-
7:52
beyond status codes! better rest http api error responses