3 ms·
It’s caught by a higher-level catch if there is one. Try blocks without a catch are a sign of any of these: poor coding, remnants from refactoring, features st
by dmitriid 7y ago
It’s caught by a higher-level catch if there is one.
Try blocks without a catch are a sign of any of these: poor coding, remnants from refactoring, features started and abandoned, possibly result of some build steps combining and optimising code.
- vimslayer 7y agoTry without a catch is fairly common and IMO quite fine when it's not the current method's job to deal with an error but it is its job to clean up state or some resources. async showImage() { this.showLoadingSpinner = true try { this.imageData = await fetchImageData() } finally { this.showLoadingSpinner = false } } There might be a parent class/component/whatever that deals with errors and shows them to the user. The image component is responsible for showing the loading spinner and it shouldn't be left spinning if there's an error.