How can I find the *actual* source of an error in my resolver?
August 2, 2019 at 1:09amThe Apollo community has a new home. This thread is preserved for historical purposes. The content of this conversation may be innaccurrate or out of date. Go to new community home →
How can I find the *actual* source of an error in my resolver?
August 2, 2019 at 1:09am (Edited 3 years ago)When a resolver triggers an exception, it seems apollo-server throws a completely useless stack trace, that points only to its own internals. I can't figure out what part of my code triggered the exception.
August 2, 2019 at 1:47am
I wonder if this is fixed in graphql-tools-fork https://www.npmjs.com/package/graphql-tools-fork
That seems like a new fork... is this a new problem? Has nobody else run into is? Everyone's fine with these useless errors? How do people figure out where errors in their resolvers are coming from?
I was hoping I was missing something obvious. Hard to believe this problem has been going on for years.
But short answer is that yes it has been broken that long. in the fort, we have made some improvements but I'm not sure how they interact with Apollo server extensions
October 10, 2019 at 5:09am
Federation is a non-starter because it doesn't support subscriptions.