@MrFallout86
Just found your channel. Pure gold. I’ve been developing for 12 years, and I’ve never seen more precise content. Sometimes it’s great to see your own approaches validated and learn new ways of working and tools on the way
@sushilb7994
This is so far the best video on Global error handling in rest api . Excellent video and eagerly waiting for the next one!!!
@mtsLeal
This playlist is incredible, I'm learning a lot of aspnet core features. Thank you so much for this!
@TheFeljoy
Really enjoying this series. I already learned a few cool things and am looking forward to the DDD parts💪
@CRBarchager
By far the best video on ErrorHandling I have ever seen. Very usefull and coincidentally what I'm about to implement in a project!
@TheScrowen
Wow, today I started to build a new app just to learn some new things. I had some questions that I haven't found answers to for a while. You've already answered the some of them. Great guide!
@MilanJovanovicTech
Interesting approach with the error endpoint. My personal favorite is using an exception-handling middleware. I also like to implement the IMiddleware interface for strong typing, it won't hurt.
@AdamBremholm
Found this series now and I must say they are so good! You manage to fit so much helpful content in such a short time, and has really opened my eyes for new areas in dotnet. Also, great to be able to follow your workflow (how to walk through other source code) and all the plugins used in vscode.
@amantinband
Really curios to hear what you thought of the video. Was diving into the framework's code useful? Would it have been better to only demonstrate the error endpoint with the factory instead of the various options?
@unhandledexception1948
These videos are so loaded with info, I have to slow them down to keep up
@nalux
I know this video has been out for a minute or two. I just want to make sure I understand the premises correctly here. The title is referring to "Global Error Handling", yet we are predominantly dealing with the aspects of an HTTP context. How is this global in any sense? I can understand the benefit and use case for this, I am merely curious about the scope for this, because Global is a rather large scope, and I don't see this error handling being able to capture something like a null ref exception in a part of the code that is not dealing with the http context. So, all in all, love the series and this video as well! Just getting somewhat confused on this specific terminology, perhaps it should be something like "Global API Error Response" or "HttpContext Error Response". Please tell me if I am totally going off my rails here :) And again, good series Amichai :)
@vivekverma30494
I love your pace. Thank you for all these detailed and direct to the point video. These videos are not for beginners but they can follow along and read about the methods and style of coding and patterns that you are following. Diving into the source code to give details of implementation is great. Really clear some of the things which happen magically.
@pratikswvk
Best video on error handling.. Thanks Amichai..
@edwardnovikov4326
finally, thanks! I'm learning asp net and did good job until that point when i realized that every extend or change led to 2-3 hours of debugging. Project was 100% monolith and i didn't know what to do. Yes, I could write working apps, but they were always very messy ;( Keep going <3
@propro8040
Hey, Thanks for putting together this great video series on data engineering! I'm really enjoying it. Keep up the great work
@RtoipKa
Probably one of the best instructional videos I have watched!
@hpdev93
Loving this series, please continue, Thank you
@ryanheitmann7591
Really enjoying the series so far, keep up the good work!
@batiku1
Great video! I'd like to note that you can actually inject a ProblemDetailsFactory either into a middleware or a filter attribute. So you can combine the benefit of using the ProblemDetailsFactory even with the 'middleware' or the 'filter' aproach.
@kmcdo