Inconsistency with form/varieties grouping
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.2k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 21
Description
In a previous issue post, forms and varieties were declared as 2 separate concepts. Forms were considered to be purely cosmetic/aesthetic changes, whilst varieties were differing in stats, typings, abilities, etc.
However, request data on the Magearna species, there are 2 varieties listed. It's standard "variety" and its Pokemon HOME "variety", with nothing but aesthetic differences.
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 requesting the Magearna species data and comparing its two listed varieties with the project’s earlier distinction between forms and varieties. Trace where these records are defined and exposed, then confirm the intended classification and verify that the API response matches it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100