Distinct on name
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.2k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 21
Description
Can we have an option for name in the distinct options? Trying to get pokemon_v2_movelearnmethod distinct on name at pokemon_v2_pokemon -> pokemon_v2_pokemonmoves -> pokemon_v2_move -> pokemon_v2_versiongroupmovelearnmethods -> pokemon_v2_movelearnmethod
query MyQuery {
pokemon_v2_pokemon(where: {id: {_eq: 1}}) {
id
pokemon_v2_pokemonmoves(limit: 20, offset: 20) {
id
level
pokemon_v2_movelearnmethod {
name
pokemon_v2_movelearnmethoddescriptions(where: {language_id: {_eq: 9}}) {
id
}
}
}
}
}
Contributor guide
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
Start with the provided MyQuery and trace the GraphQL distinct-options behavior through the pokemon_v2_pokemon → pokemon_v2_pokemonmoves → pokemon_v2_movelearnmethod traversal. Done means the distinct options accept name for pokemon_v2_movelearnmethod and the query can return results without duplicate names; verify using the shown query structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100