Link up --physical and --special Z moves to complete their data
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- api
Research direction
Start by inspecting the API data for move IDs 622–657, comparing the physical and special Z Moves and their flavour-text entries. Check the learned_by_pokemon fields for these moves and GMax moves, then confirm whether the requested links and data population are intended before validating the affected API responses.
Written by the indexing model from the issue text.
Description
The moves between 622 and 657, Z Moves, are usually identical to one another.
For example 623 is effectively the same as 622, with the only real difference being that one is physical, the other specia. I've not played S/M which is where I think this comes from - but I can understand the rational here.
The problem is that for the moves in that range id + 1 has Dummy Data in all of its Flavour Text entries. Could these be combined for completeness?
I also wanted to ask about the learned_by_pokemon fields on those moves (GMax as well). Is that data that's simply not been populated yet because of the sheer volume, or is this by choice? If every Pokémon of a certain type can temporarily use those?
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.2k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 18
Getting set up
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 PokeAPI/pokeapi
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PokeAPI/pokeapi#1684 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-2 days Newbie friendliness 76/100
PokeAPI/pokeapi#1631 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
PokeAPI/pokeapi#1623 · 3 comments ·
Maintainers usually reply within 1 day
-
UV hardlink filesOpen
Difficulty 3/5 1-2 days Newbie friendliness 48/100
PokeAPI/pokeapi#1622 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vllm-project/vllm-metal#822 ·
Maintainers usually reply within 1 day
-
vector-store
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
mem0ai/mem0#7461 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: chunk_span_bounds and _validated_chunk_spans reject Pydantic models ChunkSpan and AudioFileOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BasedHardware/omi#19047 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day