fix: sort recent files newest first - #79
Conversation
sortNodes() from @nextcloud/files inverts the sorting order when
sortingMode is 'mtime' ('asc' means most recently modified first).
Passing 'desc' therefore showed the oldest documents at the top of
the Recent list. Pass 'asc' and document the inversion.
Includes rebuilt assets.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
TL;DR: Right diagnosis, wrong tree. This branches off DetailsThe bug diagnosis is correct. Verified directly against But the live sort call isn't in this diff's target anymore. There's also already a test that pins the current (buggy) behaviour — Process note, not a blocker: the rebuilt Suggested path: close this, redo as a one-liner — |
|
You are completely right. Sorry for the mess with the branches. |
|
Implemented in #85 |
Adds four rules covering what came up while redoing #79/#83 this session: reuse existing design tokens over hardcoded values, extract components only for genuine multi-site duplication (as its own commit unless the component is new to the feature), prefer @nextcloud/vue over hand-rolled markup, and structure code for testability without extracting solely to reach a test. Signed-off-by: James Manuel <moodyjmz@users.noreply.github.com>
Every other rule in this file explains its motivating incident in the commit message or PR body, never inside the instructional text itself — #79, #83, #84, and #100's own diagnosis are all discussed there, not quoted in AGENTS.md. "see #100" broke that pattern and adds nothing: the DAV SEARCH orderby/limit example is already self-contained, and a bare PR number means nothing to a future reader without the context this conversation had. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Signed-off-by: James Manuel <moodyjmz@users.noreply.github.com>
sortNodes() from @nextcloud/files inverts the sorting order when sortingMode is 'mtime' ('asc' means most recently modified first). Passing 'desc' therefore showed the oldest documents at the top of the Recent list. Pass 'asc' and document the inversion.
Includes rebuilt assets.
🤖 AI (if applicable)