Differences in different APIs handling forms
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.2k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 21
Description
Not sure if bug report or feature request, but I suppose it's a feature request
I spent a long, long, long time trying to debug this. Apparently:
https://pokeapi.co/api/v2/pokemon-species/ has giratina-altered as a 404 but giratina returns data
https://pokeapi.co/api/v2/pokemon/ has giratina as 404 but giratina-altered returns data
I'd love for this to be consistent. Obviously form differences don't have different dex entries, but can have different stats for example. I also realize of course we wouldn't be making existing APIs now return a 404. However, my suggestion is simply for giratina to redirect to giratina-altered for the pokemon-species API and to have giratina-altered redirect to giratina for the pokemon API.
Thank you in advance!
Contributor guide
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.
Research direction
Start by comparing the pokemon-species and pokemon API entry points for giratina and giratina-altered, including their current 404 behavior. Confirm the intended compatibility behavior with the existing API responses; done means the two form names resolve consistently without breaking the currently valid endpoints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100