Question

17

TypeScript/Angular try catch, any error in try block not going to catch block

rated 0 times [ 21] [ 4] / answers: 1 / hits: 65694 / 6 Years ago, wed, may 23, 2018, 12:00:00

I am using Angular and TypeScript.
I have used try catch construct for error handling in case of API call.
If any error occurs in try block it is simply NOT going to catch block.
App terminates there only.

I have tried using throw as well.
Here is a sample code snippet,

try {



  this.api.getAPI(Id).subscribe( // this.api is my api service and getAPI is present there

    (data: any) => {

      if (data == null) {

        throw 'Empty response';

      }

    },

    (error: HttpErrorResponse) => {

      console.log(error);

    };



} catch(e) {

  console.log(e); 

}

in some cases 'data' from API returns 'null',
but throw is not going to catch block
ALSO, tried without throw, it gives null error for 'data' ... in that case also not going to catch block.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

kaleyv

Add To Favorites

Follow

Total Points: 259

Total Questions: 99

Total Answers: 107

Location: Saint Helena

Member since Tue, Nov 3, 2020

4 Years ago

kaleyv questions

1 How can I calculate the total price of products in a cart using JavaScript?

Sun, Jan 16, 22, 00:00, 2 Years ago

1 array.map() is returning elements all together in React JS

Thu, Dec 16, 21, 00:00, 2 Years ago

1 How do I reset mocked values in Jest?

Sat, Oct 24, 20, 00:00, 4 Years ago

1 NuxtJS: Disable console.log in production env

Sun, Oct 18, 20, 00:00, 4 Years ago

1 forwarding ref to react.FC gives type error: Property ref does not exist on type 'IntrinsicAttributes & Props & { children :? ReactNode}

Wed, Sep 16, 20, 00:00, 4 Years ago

View All

answered 6 Years ago ryder · Accepted Answer

A try/catch won't catch anything in a callback passed to subscribe (or then, or setTimeout or anything smiilar) which runs on a different tick or microtask. You have to catch errors in the task where they occurred.

I could suggest better alternatives if I understood what you were trying to do when the error occurred. If all you really want to do is to log it, you could of course do that right after the check for null.

You might consider mapping the observable prior to consuming it and issuing an error on the observable in case of a null, such as:

const checkedData = this.api.getAPI(Id).pipe(map(data => {

  if (data === null) return throwError(null data);

  return data;

});

Now you can subscribe with

checkedData.subscribe(

  data => /* do something with data */,

  console.error

);

Note: throwError is rxjs6. For rxjs5, it would be return ErrorObservable(null data) (I think).