-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Core::throwError should throw error and not an object #21
Comments
After going through the source code, detail there is probably what you're looking for? |
@wodka, You may write wrapper callback function and try to use Sentry from there. Please let us know if this is feasible for you. |
@ralph-remo it's really more about allowing other tools to use the primitives of javascript to detect errors. This is harder when using objects that are not extending Error. @cb-niravjadav I've just created a PR #25 with a new env config option |
Further: https://github.com/chargebee/chargebee-typescript/blob/master/README.md#error-handling mentions that is should be possible to check for the param in the error. That value is never set? Should this be the general area / resource? |
Currently the throwError static function will return an object and not an error.
chargebee-typescript/src/core.ts
Line 174 in d0a0bc6
This makes it problematic in terms of using it in other error management tools like Sentry.
The text was updated successfully, but these errors were encountered: