{"id":823,"date":"2025-05-06T07:25:17","date_gmt":"2025-05-06T07:25:17","guid":{"rendered":"https:\/\/www.wordpress-prod.sharpener.tech\/?p=823"},"modified":"2025-05-24T14:25:56","modified_gmt":"2025-05-24T14:25:56","slug":"error-handling-try-catch-finally-block","status":"publish","type":"post","link":"https:\/\/www.sharpener.tech\/blog\/error-handling-try-catch-finally-block\/","title":{"rendered":"Error Handling -(Try-catch-finally-block)"},"content":{"rendered":"\n
\"Error<\/figure>\n\n\n\n

Hello everyone. I hope you are doing well.<\/p>\n\n\n\n

I am Julian Toppo and today we will learn more about error handling and it\u2019s implementation. We will also learn how we handled empty input values in the previous video. <\/p>\n\n\n\n

Error handling is like having a plan or dealing with mistakes when they happen.<\/p>\n\n\n\n

Let me share a story about a to-do app I created. <\/p>\n\n\n\n

I was excited that my friends would use it, <\/p>\n\n\n\n

but soon, they started facing problems.<\/p>\n\n\n\n

The app crashed when users submitted tasks with empty fields or special characters.<\/p>\n\n\n\n

This was because my code didn\u2019t handle errors properly. <\/p>\n\n\n\n

Luckily, I learned my lesson about the importance of error handling.<\/p>\n\n\n\n

Let\u2019s try to understand error handling <\/p>\n\n\n\n

by taking an example of an airport security check.<\/p>\n\n\n\n

Airport security is strict. <\/p>\n\n\n\n

They have clear rules on what you can bring.<\/p>\n\n\n\n

For example, you can only carry 100 ml of liquid. <\/p>\n\n\n\n

You can\u2019t bring flammable items like lighters. <\/p>\n\n\n\n

Sharp objects like knives are also not allowed.<\/p>\n\n\n\n

These are the basics, but rules can vary a bit .<\/p>\n\n\n\n

-Why do you think there\u2019s so much strictness? <\/strong><\/p>\n\n\n\n

Let a person with a gun sneaks into the airport.
This is dangerous for everyone. It could disrupt airport operations.
To prevent this, we check for weapons during security.
This way, we stop problems before they start.<\/p>\n\n\n\n

So Being proactive helps keep everyone safe.<\/p>\n\n\n\n

Similarly in coding<\/strong>:<\/p>\n\n\n\n

Errors can crash your app or cause incorrect results.
Instead of waiting for a crash, we handle errors ahead of time.<\/p>\n\n\n\n

(New Additions after this)<\/p>\n\n\n\n

Implementation Example:<\/strong><\/p>\n\n\n\n

Let\u2019s go back to the example of a form
When we are writing code to read the name and age value in the form
errors can come anywhere.
In this code, the error could occur if there\u2019s a misspelled word or
if we are trying to access something that is not present.
Let\u2019s say (referring to the code) we are trying to access the name using the event. target,
But wait we have misspelled the word name and we are using \u201c.value\u201d for it.
This will result in standard predefined errors like Type errors .
This will cause our application to work incorrectly.
Take a look:
Wouldn\u2019t it be better if we could handle the code,
without disrupting the flow of our application.
For implementing this we enclose the code which will result in possible errors inside the try block.<\/p>\n\n\n\n

This will ensure that any potential error inside the block is handled.

Will show the code implementation of error occuring using.<\/em><\/p>\n\n\n\n

Catch:<\/strong><\/p>\n\n\n\n

Now that error is occurring. Who will handle it?
The error occurring in the try block is caught by the catch block. <\/p>\n\n\n\n

Let\u2019s have a look:
It processes the error, typically by logging an error message or performing other error recovery actions.
This helps us in handling errors more efficiently without crashing the whole application or displaying incorrect results in our case no results.<\/p>\n\n\n\n

Will show the code implementation of error handling using code.<\/em><\/p>\n\n\n\n

Throw: <\/strong><\/p>\n\n\n\n

In addition to handling standard errors such as Type Errors, Reference Errors, and Syntax Errors,
we can also raise custom errors based on specific conditions in our code.<\/p>\n\n\n\n

Extra custom errors help us specify problems easily,
which makes fixing them simpler.
They also give clearer messages to developers and users, making the app work better.<\/p>\n\n\n\n

For example, if we need to check that the name and age fields aren’t empty,
we can create a custom error.
If either field is empty, it will show a message like,
Value of age or name cannot be empty.\u201d
This message is one we’ve created to improve the app and is
not just a standard JavaScript error.<\/p>\n\n\n\n

Let\u2019s take a  look at how we can implement this.<\/p>\n\n\n\n



If we go by the traditional format of checking whether the element is empty or not.<\/p>\n\n\n\n