PokeAPI / PokeAPI/pokeapi

Graphql cannot provide nested pokemon species

Open
#924 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
5.4k
Forks
1.2k
Avg merge
2d 5h
Merged PRs (30d)
21

Description

It seems like the graphql API is unable to provide a pokemon species data when nested under pokemon -> pokemonspecy.

This query returns an empty array as pokemon_v2_pokemonspecies

query samplePokeAPIquery {
  pokemon_v2_pokemon(where: {name: {_eq: "charizard"}}) {
    name
		pokemon_v2_pokemonspecy {
			pokemon_v2_pokemonspecies {
				name
			}
		}
  }
}

This query returns a valid response (but requires a separate query).

query samplePokeAPIquery {
  pokemon_v2_pokemonspecies(where: {id: {_eq: 64}}) {
    base_happiness
    capture_rate
    id
  }
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the nested and separate GraphQL queries from the issue and compare their responses. Trace the relationship between pokemon_v2_pokemon and pokemon_v2_pokemonspecies in the GraphQL API; done when the nested query returns the species data for Charizard instead of an empty array.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.