thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (THRIFT-3916) Errors thrown from JavaScript client is strings and not errors
Date Wed, 01 Aug 2018 16:20:00 GMT


ASF GitHub Bot commented on THRIFT-3916:

jeking3 commented on issue #1075: THRIFT-3916 Throw proper errors from JS, not strings
   Original author has not responded to any comments and PR needs more work.  Closing the

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Errors thrown from JavaScript client is strings and not errors
> --------------------------------------------------------------
>                 Key: THRIFT-3916
>                 URL:
>             Project: Thrift
>          Issue Type: Bug
>          Components: JavaScript - Compiler
>            Reporter: Simen Bekkhus
>            Priority: Minor
>              Labels: javascript
> In JavaScript, you can {{throw}} any object, including strings, but to get stack traces
one should throw {{Errors}}.
> The generated JS code throws the error string directly, instead of wrapping it in {{new
> Node core _only_ rejects with/throws Errors, never strings, and Thrift should follow
the same standard.
> {quote}
> All errors generated by Node.js, including all System and JavaScript errors, will either
be instances of, or inherit from, the Error class.
> {quote}
> PR for the change [here|].

This message was sent by Atlassian JIRA

View raw message