-
Notifications
You must be signed in to change notification settings - Fork 23
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
Try to use the GraphQLError class to produce the error #175
base: main
Are you sure you want to change the base?
Conversation
This doesn't address the root cause of an unexpected error, but it makes the transtion of the error back through the router a little cleaner.
By looking up how typescript works in google and attempting to write some.
Signed-off-by: Benjamin Coenen <[email protected]>
Signed-off-by: Benjamin Coenen <[email protected]>
…rypen/1519-slghtly-better-errors
Signed-off-by: Benjamin Coenen <[email protected]>
Signed-off-by: Benjamin Coenen <[email protected]>
Signed-off-by: Benjamin Coenen <[email protected]>
@@ -215,18 +214,17 @@ async function run() { | |||
}); | |||
} | |||
} catch (e) { | |||
logger.warn(`plan_worker: an unknown error occured ${e}\n`); | |||
logger.warn(`plan_worker: an unknown error occurred ${e}\n`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also fix a typo.
I already tried, it produces a bad bundle.js with require inside and deno is unable to launch with |
Yeah, I know. I wanted to see why. We already use |
I am concerned this doesn't work and I'm going to leave this PR open for now. |
Just to test this approach