Evaluate full API surface for anything unnecessary
@imnasnainaec is already working on this.
Since Sep 25, 2026.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Review the library's public functions, arguments, and user documentation against real user stories, then document which API surface is unnecessary and the criteria for deciding what should remain.
Written by the indexing model from the issue text.
Description
Are there functions, arguments, or user doc details that aren't relevant to any real user story?
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 9d 14h
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from sillsdev/python-sil-lift
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
sillsdev/python-sil-lift#15 ·
-
bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
sillsdev/python-sil-lift#45 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 72/100
sillsdev/python-sil-lift#35 ·
-
Media hrefs resolve case-sensitively: Windows-authored folders get false missing-media on LinuxPossibly taken @imnasnainaec claimed this 12 days ago. Openbug
Difficulty 5/5 Over a week Newbie friendliness 38/100
sillsdev/python-sil-lift#34 · 1 comment · 1 assignee ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 72/100
sillsdev/python-sil-lift#33 ·