Numbering system for variants?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 378
- Avg merge
- 22h 18m
- Merged PRs (30d)
- 25
Description
I'm using these sprites in a personal project and supplementing them with artwork from Sun & Moon. I'd like to contribute back to the PokeAPI project by submitting a pull request with this content, along with whatever data I contribute to the core. However, there are many variants (Alola forms & identical Pokemon species with different appearances and typings), and I'm curious how the project tackles these.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Review the repository's existing sprite and variant data conventions, then use the discussion to determine whether a numbering approach is wanted and what the accepted handling of alternate forms would be; done means an agreed project direction rather than an implementation defined by this issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100