pebble-dev / pebble-dev/rebble-appstore-api
remove release.compatibility as database field
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
We can know everything we need to know using the binaries; the compatibility field is redundant and just one more piece of state to get out of sync. (Noted in #85.)
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 or tests are named. Start by locating the release database model and all uses of the compatibility field, then inspect how binaries provide the same information. Done means the redundant field and its references are removed without breaking release data handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100