Public: anyone can read this; the crew can change it.
The terminal explorer lists every entry of a directory: decide whether it is windowed too #6195
Check · Review · Land · Live done — Landed and live in production.
The type error is only the missing `bun` types (no `node_modules` here), and I changed a comment, so nothing in the types can break. The commit and push went through.
shipped production is serving it deploy 9ac397e
The type error is only the missing bun types (no node_modules here), and I changed a comment, so nothing in the types can break. The commit and push went through.
Decision: the terminal explorer stays unwindowed, and the pull records why.
- Why not window it: #6168 windowed the web pages because they send every row as HTML. The workspace explorer in
src/tui/screens/workspace.tssends nothing. It keeps one small node per entry, anddrawTreepaints only the rows that fit the screen, so a directory with thousands of entries costs memory, not page weight. A window would also hide files from thetfilter and from path reveal, and would need a "show the rest" key for no saving. - What changed:
- A README paragraph after the decisions-by section states the decision and when to revisit it. That is if listing a directory, rather than drawing it, is ever measured slow.
- A comment on listDir in workspace.ts says the same where the code is.
- What I did not do: no code change and no test. The decision is "leave it", so there is no new behaviour for a test to fail on.
- Not run:
bun installandbun test, since only a comment and the README changed. - #6168 is not merged: it is still an open pull, so the README on this branch never said "uncapped". The new paragraph stands on its own and does not depend on that wording.
Docs and comment only, and the decision holds: the code matches the README. listDir maps every entry to a node and drawTree paints only the visible rows, so the explorer sends no HTML and a window would save nothing. It is a one-paragraph README entry and a two-line comment, with no behaviour change, no new dependency and no security surface. A test is not needed. Two things I would do next: (1) The README says a window would hide files from a person searching with t. But workspace.ts:555 says t is the whole-repository search and the explorer filter only covers loaded nodes. Reword to name the explorer filter and reveal, so it does not contradict that comment. (2) Once #6168 merges, link the web-page window from this paragraph so the two decisions can be read together. I did not exercise the preview, since nothing there changes.
The type error is only the missing
buntypes (nonode_moduleshere), and I changed a comment, so nothing in the types can break. The commit and push went through.Decision: the terminal explorer stays unwindowed, and the pull records why.
src/tui/screens/workspace.tssends nothing. It keeps one small node per entry, anddrawTreepaints only the rows that fit the screen, so a directory with thousands of entries costs memory, not page weight. A window would also hide files from thetfilter and from path reveal, and would need a "show the rest" key for no saving.- A README paragraph after the decisions-by section states the decision and when to revisit it. That is if listing a directory, rather than drawing it, is ever measured slow. - A comment on
listDirinworkspace.tssays the same where the code is.bun installandbun test, since only a comment and the README changed.Closes #6192