NotifiableError typed to any

Hi, I was just wondering why NotifableError is typed to any when it doesn’t accept any?

I naively passed in an unknown response object to client.notify() and get no errors in typescript yet in production I get the not so helpful Bugsnag usage error. notify() expected error/opts parameters, got unsupported object. This is exactly the sort of error typescript is great for avoiding. If the any type was removed from the below I would’ve got this right first time:

 export type NotifiableError = Error
  | { errorClass: string; errorMessage: string; }
  | { name: string; message: string; }
  | any;

Am I missing something? It seems like dropping any would resolve the runtime issue by catching it at compile time.

[xljones]

Hi @toxaq, a fix for this was released in v7.0.0

[toxaq]

Hi @bengourley ! Appreciate the response.

Old school Visual Studio C# dev here but since moved on to OSX now with typescript. So I appreciate the benefits of intellisense autofill but the real benefit to me is the typescript compiler, so dropping any would’ve flagged my runtime issue well before finding the unsupported object logs in bugsnag.

The 3rd party library is precompiled minified javascript, so whilst I could trawl through it, all I know is it returns an error object, just not an actual Error object. So for me the ideal solution would be that bugsnag would fall back to stringifying the unknown object and would be happy if the error name was received unknown object and the message was the object values. That way with the information of the object I could better handle it and even write some tests based on an exact object.

Thanks for taking the time to look at this.