Fix: Removed regional restrictions so Rattata can evolve into Raticate in any region#1308
Fix: Removed regional restrictions so Rattata can evolve into Raticate in any region#1308joereg4 wants to merge 3 commits intoPokeAPI:masterfrom
Conversation
…ata in specific rows to ensure consistency.
Fix: Removed regional restrictions so Rattata can evolve into Raticate in any region
|
Hi! Rattata is the only one I checked, could you human-verify some other additions we merged? Also, where did you get the data from? |
|
A script that cycled through the bulbpedia API |
|
Hi, Ninetales has the same problem: https://staging.pokeapi.co/api/v2/pokemon-species/38 leads to https://staging.pokeapi.co/api/v2/evolution-chain/15/ that states that Ninetales needs to be in region I think you need to revise your script and adjust the data. |
|
In the meantime I'll remove all the CSV data you've added so we can resume merging other PR and publishing to prod. |
|
@Naramsim I have taken a different approach. To make this work we need new evolution chains for the regional variants. Simply adding the region_id works for those that have two chains like this: Meowth -> Persian, not locked to any Region (Chain 34) And we won't need the base_form_id. I'll resubmit with the region for these: base_form_id,base_form_name,required_region,required_region_id,reason And then start working on evolution chains for Regional variants such as these since they conflict with the base form: evolution_chain_id,name,region,region_id,base_form_id,base_form_name This last part will take more time. |
The evolution data for Rattata → Raticate was incorrectly restricted to the Alola region only, preventing the evolution from occurring in other regions. This was identified by @Naramsim in the review of the evolution data.
Issue Details: