Show how many threads are open in each file of the file list
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, markdown
- Domain
- frontend
Research direction
Start by reading issue #199, which defines the boxed aside threads this count depends on, then trace how the file list detects file changes and displays folders. Add counts for unticked boxed asides beside files and aggregate them for folders; verify that unboxed asides do not count and that counts update when a file changes. The payload names no source files or tests, so locate the relevant entry points in the project.
Written by the indexing model from the issue text.
Description
Nothing in the file list says which files have a conversation still open, so finding what's waiting on you means opening each one.
-----
reviewer #: Josh
reviewer c: Claude
-----
The tracks game can't be finished.
~# [ ] I can't connect the last track to B
~~c It's a bug; fixed in 316bc92.
Puzzles need a number pad on a phone.
~# [x] Should this be its own issue?
~~c Filed as #246.
A thought of my own, not a thread.
~ worth a post
To try it: save that as review.md in a folder of several files, and open the folder in reader.
What happens: review.md looks like any other file in the list.
What should happen:
- A file with open threads shows a small count beside its name in the file list, here
1: a thread is an aside with a box (#199), and it's open until its box is ticked. - Asides without a box, as in notes, never count, so a file of your own notes shows nothing.
- A folder shows the total of the files in it, so a day's review folder says whether anything is left.
- The count updates when a file changes, as the list does.
Depends on #199.
Came up in the retro of the 2026-11-04 review.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 26
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 jzheaux/reader
-
polish
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
polish
Difficulty 3/5 1-2 days Newbie friendliness 64/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OWASP/CheatSheetSeries#3018 ·
Maintainers usually reply within 1 day
-
Radix number block generates NaN after switching a negative or decimal number to binary, octal or hexPossibly taken @matthewalberto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mit-cml/appinventor-sources#4246 · 1 comment ·
Maintainers usually reply within 1 day
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
GoogleChrome/modern-web-guidance-src#3675 · 2 comments ·
Maintainers usually reply within 1 day