lucasw89/gacha-event-tracker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: name the sorting rule rather than counting bullets to it

Browse Source 
A cross-reference by position ("two bullets down") was already wrong by one,
and would go wrong again the next time something is inserted above it.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
Lucas Winther
2026-08-18 03:33:33 +02:00
co-authored by Claude Opus 5
parent e489697540
commit 07937b4c14
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+3 -3
View File
@@ -440,9 +440,9 @@ to an open page). Four things hold it up:
is long, so a full-height divider would spend most of its length walling off a gap. is long, so a full-height divider would spend most of its length walling off a gap.
- **Truncating a list is not re-sorting it.** Each section shows `LIST_CAP` rows and offers "show - **Truncating a list is not re-sorting it.** Each section shows `LIST_CAP` rows and offers "show
all N". The rows below the cut keep their place in the order, stay counted in the header, and stay all N". The rows below the cut keep their place in the order, stay counted in the header, and stay
on the timeline — so the deadline guarantee two bullets down holds for what is hidden exactly as it on the timeline — so the *sorting groups, it never reorders* rule below holds for what is hidden
does for what is shown. Expanding is per-visit state, not a stored preference: it is something a exactly as it does for what is shown. Expanding is per-visit state, not a stored preference: it is
reader does while reading one list, not a statement about how the app should work. something a reader does while reading one list, not a statement about how the app should work.
- **Which view opens is the reader's answer.** `prefs.view` is asked once on the first run (PRD F8) - **Which view opens is the reader's answer.** `prefs.view` is asked once on the first run (PRD F8)
and written by the tabs from then on. It was component state, which meant a reader who preferred and written by the tabs from then on. It was component state, which meant a reader who preferred
the timeline was put back on the list by every reload, with nothing to blame but the app the timeline was put back on the list by every reload, with nothing to blame but the app