UI: Reading indicator is wrong
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
The issue identifies a reading indicator computation but gives no component file, test, or expected calculation. Start by locating the reading indicator component and its existing tests, then trace how it computes progress. Done means the indicator reflects the correct reading progress, with a test covering the calculation.
Written by the indexing model from the issue text.
Description
Observation
The component gets its computation wrong to adjust the progress indicator accordingly. There is not much to add.
Solution
Get the computation right.
- Dominant language
- Python
- Stars
- 123
- Forks
- 31
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 47
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 ip-tools/patzilla
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ip-tools/patzilla#139 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
UI: Update BabelOpendependencies help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
dependencies help wanted javascript
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
dependencies javascript
Difficulty 3/5 1-2 days Newbie friendliness 66/100
ip-tools/patzilla#125 · 1 comment ·
Maintainers usually reply within 1 day
All issues in ip-tools/patzilla
Similar issues
-
follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
modelscope/modelscope#1833 ·
Maintainers usually reply within 1 day
-
ocr_data_to_elements() raises AttributeError when a layout element is a ListPossibly taken @Eapp1e claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Unstructured-IO/unstructured#4616 ·
Maintainers usually reply within 1 day