I never knew how to actually use React Error Boundary until now. Also didn't know how much of an improvement it is over the native React error boundary. Thanks for the knowledge.
I've been using the react error boundary but didn't know it could catch errors from async operations, also I didn't know of the limitation of the error boundary. Thanks for the video
Hey. Nice video! However i have a feeling that if you would throw an error in catch after fetch items, the native react boundry would pick it up. This is the the step you also need to do using library (calling method from hook).
So, because he points out a junior mistake, that means he cant also make a mistake? Junior devs cant recognize junior mistakes? If I may say so, that is junior dev type of thinking 🤌
Hello there, I am beginner learner of react. please make separate tutorial on react-error-boundary, describing everything. I hope new tutorial on react-error-boundary will come soon.
You can use a function component as a fallback in the native error boundary... I don't see the point in downloading an extra bloating package, am I missing something?
Well, what I do - I have a global reduxToolkit state just for error and if anything sh1tty happens in try/catch + fetch, I will just return that error to the redux error component which displays the error message to the user as a modal. I will look at this though. I did not know about this library. Thank you!
There is a problem with example 2. You passed the error to the catch block and did nothing with it. How do you expect it to be caught by the ErrorBoundary?
Is the react-error-boundary library a good replacement for the built-in React ErrorBoundary component if: - you would like a fallback ui for asynchronous error as well as regular errors - if you don't like to use React class components Did i understand that correctly anything else i am missing?
redux or interceptor ma rakhyo bhane ta harek euta component ma gayera feri error ko lagi ui milairakhnu paryo tyo package use garyo bhane kunai component ma error aaye ni tesle handle gardincha so tyo sajilo bhayo
What you explain in what React tells you to use for 'ErrorBoundary' is fucking baffling. Thanks for helping me understand this, so I now need to wrap the child and not use the async that should be throwing it... Makes sense. Thank you.