Show how many threads are open in each file of the file list

Open
#255 0 comments 0 reactions 0 assignees View on GitHub

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

enhancement

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jzheaux/reader

All issues in jzheaux/reader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.