Skip to content
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

Expose machine-readable cause of error in callback result #15

Open
daniel-j-h opened this issue Apr 24, 2017 · 0 comments
Open

Expose machine-readable cause of error in callback result #15

daniel-j-h opened this issue Apr 24, 2017 · 0 comments

Comments

@daniel-j-h
Copy link
Contributor

In case of an error in the bindings we use SetErrorMessage in both the TSP and VRP worker to let NAN generate an Js Error for us. What we should add is not only a message but also a parse-able code, think:

{code: 'Timeout', message: 'Unable to find a solution, solver timed out'}

Implementation: in the async. workers override

void HandleErrorCallback()

and generate a Js Error object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant