PokeAPI / PokeAPI/api-data

Query about Mr. Mime's evolution chain correctness

Open
#274 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
189
Forks
55
Avg merge
4h 40m
Merged PRs (30d)
17

Description

I wanted to enquire about whether anyone agreed with me that Mr. Mime's evolution chain should be modified.

This might just be something that suits my project, so feel free to say "nah it's how it's intended"!

Currently it's Mime Jr. -> Mr. Mime -> Mr. Rime (https://github.com/PokeAPI/api-data/blob/8ff36d31b496facb2c43b65031d6e74212f6a15f/data/api/v2/evolution-chain/57/index.json#L75)

AFAIK the actual reality is: Mime Jr. -> Mr. Mime and Galarian Mr. Mime -> Mr. Rime

So would it be best to split the evolution chain in two, otherwise the only assumption you can really make from the data is that Mime Jr. can evolve all the way to Mr. Rime, which I don't believe is the case?

I could be wrong, I've not played most of the games, but what I've said is true in Pokemon Go at least!

I'd be happy to raise a PR with the change if it's agreed upon, just wanted to see what people thought before I went to the effort of figuring it out!

Contributor guide

No contributing guide indexed for this repository

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 with data/api/v2/evolution-chain/57/index.json at the referenced lines and compare its Mr. Mime, Galarian Mr. Mime, and Mr. Rime relationships with the intended game data. Confirm the project’s expected treatment of regional forms; done means the evolution data accurately represents the separate chains, if maintainers agree that a change is needed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.