Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow combineResolvers and pipeResolvers to reject
See original GitHub issueFirst off, thanks for this very useful library.
The issue I’m running into is with how combineResolvers and pipeResolvers have a .catch that returns the error, rather than allowing the error to bubble up. This seems to be counter to how a regular resolver would work.
Currently, as I user of the library, If I want to act on an error occurring in the resolver, I have to use instanceof on the resolved value and if it’s an Error, act appropriately. If I want to allow graphql to just add the error to the errors array in the response, then I have to check with instanceof and if Error re-throw.
Perhaps I’m using it wrong, but I seems like it should be up to the code using the library to decide how error should be handled.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sorry, sir. Done 😉
Sorry, @brandondoran. It is under a beta flag:
yarn add graphql-resolvers@beta