Failure when api adds new types to GraphQL interfaces
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
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.
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
- Dominant language
- Go
- Stars
- 2
- Forks
- 5
- Avg merge
- 3h 49m
- Merged PRs (30d)
- 34
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from nais/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
Maintainers usually reply within 1 day
-
mcp: mock schema is invalid GraphQL, so schema_* tests pass on a parse errorPossibly taken @Starefossen claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
mcp: schema_list_queries returns an array as structuredContent, and its outputSchema is invalidPossibly taken @Starefossen claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
microcks/microcks-cli#608 · 1 comment ·
Maintainers usually reply within 1 day
-
bug from-studio
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esengine/DeepSeek-Reasonix#14868 ·
Maintainers usually reply within 1 day
-
Install notes print "Camunda REST API: https://" without a host when global.host is setPossibly taken @irisfield claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
camunda/camunda-platform-helm#7790 ·
Maintainers usually reply within 1 day
-
[Bug]: zot exits with code 0 when it can't startPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
project-zot/zot#4636 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
keyxmakerx/Chronicle#1911 ·
Maintainers usually reply within 1 day