brandonchinn178 / brandonchinn178/graphql-client
`GraphQLError` has no `Exception` instance
Open
- Dominant language
- TypeScript
- Stars
- 24
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
This means that `GraphQLErrors` are difficult to deal with, cannot be wrapped as a `SomeException`, and have no `displayException` function to display them nicely.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the GraphQLError definition and the existing error-related tests or entry points. Check how GraphQLError is currently represented and handled, then make it usable as an Exception with a clear displayException result; done means it can be wrapped as SomeException and displayed nicely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100