Add property to Pokemon model containing its past types #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Any idea of when/a schedule for production PokeAPI to be updated to include changes from staging? Additionally, I'm open to including some option to allow for |
|
@mtrdp642 sorry for the delayed response! I can confirm that the past type data is in the production PokeAPI now, you can see them by querying |
jtwotimes
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a property to the Pokemon model containing its past types.
The data was added to PokeAPI in this PR: PokeAPI/pokeapi#457
This should NOT be merged until the data is available in the production deployment of PokeAPI; it is currently only available in the staging deployment, e.g. https://staging.pokeapi.co/api/v2/pokemon/35/.