Failure when api adds new types to GraphQL interfaces
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 5
- Avg merge
- 17m
- Merged PRs (30d)
- 11
Description
When the API returns a new type from a query returning an interface, the client is throwing an "unexpected concrete type for" error.
So it requires pulling the schema and then regenerate graphql. We should look into how not to throw an error, given that the interface fields should be enough
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the GraphQL client code that handles interface results and produces the "unexpected concrete type for" error, then reproduce the failure with a newly returned API type. Done means the client no longer requires schema regeneration for this case and tests cover the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100