-
-
Notifications
You must be signed in to change notification settings - Fork 955
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add past Pokemon type data #457
Conversation
They were all Electric-Ghost type prior to Generation V
Whoa, @phrasmotica thanks for the amazing work! But maybe it was better to open an issue before doing all of this. Right now we fetch our data from Veekun so we are using directly their files, without touching them. We don't really want to fix or add files by ourselves. Maybe you can open an issue at Veekun (https://github.com/veekun/pokedex) and check what do they think about adding a pokemon_types_past.csv file. I'm not saying that we don't like your contribution but I can say that we will hardly merge it if Veekun doesn't integrate it. Will you please open an issue at Veekun and link this one here over there? Thanks again!! |
@Naramsim thanks for the kind words! I did rush into making the changes and opening this PR without asking what the process is... this is some data I'd like to use in a project of mine, after all! I'll open an issue in Veekun's Pokedex and link it to this one 😄
|
Hey! I've just come back to this project and seen that a break's being taken from using Veekun's data. Any chance I can revive this issue and add the data directly? I'm in the process of merging master back into my branch.
|
Aha, I see that there is a fork of Veekun's pokedex repo in this project. Should the stuff in this PR be merged there instead? |
Hi @phrasmotica, thanks for sticking with us :) You can just keep this PR open. I'll need to review it again as I don't remember its contents. But basically, you've added a new CSV file that keeps track of changes to the types of pokemon, right? |
@Naramsim exactly! My original comment describing the change is still accurate. And thank you for revisiting this :) |
Alright, I looked at the diff and built it. Whenever I try to query the local API I get a 500.
Does it also happen to you? The build works fine. |
@Naramsim after checking out the branch fresh, running |
Nice, I did it. I had to remove the docker volume. So the Django So @phrasmotica, everything works very well! Thanks for the contribution and also for writing the tests! I'm merging. Also, we need to integrate the changes you made to our |
A PokeAPI/api-data refresh has started. In 45 minutes the staging branch of PokeAPI/api-data will be pushed with the new generated data. |
The updater script has finished its job and has now opened a Pull Request towards PokeAPI/api-data with the updated data. |
These changes add data describing a Pokemon's types in a previous generation. All Pokemon that have different type(s) to when they were first introduced are included, and are as follows:
The new CSV file has entries containing the Pokemon's ID, the last generation in which they had the listed type, the type and its slot.
A Pokemon resource now has a
past_types
JSON field:The API README file has been updated with an explanation of the new data and example JSON from Clefairy.
Data derived from https://bulbapedia.bulbagarden.net/wiki/Category:Pok%C3%A9mon_that_have_had_their_type_changed.