Expose Move_Effect in API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.2k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 21
Description
It would be kinda interessting for data research (at least for me), to expose the Move_Effect table in API.
I have an issue in my code, where apparently the short_effect of multiple Move_Effects is the same, compared to their long_effect, (ignoring that all of them in the change for #1031 now have the move effect chance in there), so i cant just group by the effect prose when looping over the list of moves to get.
Knowing that there are 1k moves, but only ~400 move effects, makes me wanna know what the most used move_effects are overall. (Count how many pokemon knows a move, then group by move_effect, and do some filtering on the moves if needed).
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
Begin at the API entry point that exposes move data and trace how the Move_Effect table is represented; compare short_effect and long_effect handling, including the change from #1031. Done means clients can retrieve Move_Effect records and distinguish their fields for aggregation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100