aboutsummaryrefslogtreecommitdiffstats
path: root/tools/feed-media-views-test.js
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-10-16 17:22:35 -0700
committerAdam Soltys <[email protected]>2026-10-16 17:22:35 -0700
commitef3ea098ef8b370ac71e0c3a5b638625556b0937 (patch)
tree329982d66991f464090fcc28363e8bb5edc64678 /tools/feed-media-views-test.js
parent885bc2647a3558554a53a794f1d56e9dbd7657e6 (diff)
downloadcoinosv3-ef3ea098ef8b370ac71e0c3a5b638625556b0937.tar.gz
coinosv3-ef3ea098ef8b370ac71e0c3a5b638625556b0937.zip
Conversations is a view of every feed — the chip beside Notes, Images, Videos and Articles — not a feed of its own.
Adam, 2026-10-16: "conversations [should] be one of the filter chips between all and images and all should become notes". So the view row reads Notes · Conversations · Images · Videos · Articles, and Conversations shows the current feed's people in reply — Following, Popular, a list, a topic, a pack, anyone's timeline — each reply under the post it answers, as 885bc26 drew them. The view is a feed state of its own under the feed's id (suffix ~replies: its own notes, clock, disk cache, fresh counter and live watch), with a definition derived from the feed's (replies: true) so the merge, seeding, borrowing, watch and kinds all go by it unasked; Notes ↔ Conversations is entered like a switch of feed, the feed chip unchanged, and the chosen view persists across feeds and reloads like the others. A feed's state is forgotten together with its view's (dropFeedState) when its query or relays change or it is deleted. The built-in Conversations feed chip and the editor's "Replies instead of posts" toggle from this morning are gone with it (def.replies stays as the derived definition's mark). tools/feed-conversations-test.js follows: the view chips in order, no feed chip of its own, the view's cache under following~replies, the feed chip staying on Following while the view is on, Back landing on the view, a new list feed opening straight into the view with the replies borrowed from the feeds in hand and Notes giving its posts, Following's view back at once, and a reload opening on the view from its own cache. feed-media-views-test names the chips; feed-custom-test is back as it was. feed-media-cache-test is flaky either way (a stray first page in its request window, or its 8 s timing, on clean HEAD too); feed-custom-test's "lands in Everything" fails on clean HEAD; the other feed suites pass. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01J1Kon8bxJoHRpJdSzshCkp
Diffstat (limited to 'tools/feed-media-views-test.js')
-rw-r--r--tools/feed-media-views-test.js4
1 files changed, 2 insertions, 2 deletions
diff --git a/tools/feed-media-views-test.js b/tools/feed-media-views-test.js
index 2c84b14..14a9803 100644
--- a/tools/feed-media-views-test.js
+++ b/tools/feed-media-views-test.js
@@ -126,8 +126,8 @@ try {
await page.waitForSelector('.notes-feed:not([data-booting])', { timeout: 20000 });
console.log('\n[the switch]');
- check('All / Images / Videos / Articles sit under the chips, All on', await page.evaluate(() =>
- [...document.querySelectorAll('.media-mode')].map((b) => b.textContent + (b.classList.contains('on') ? '*' : '')).join(',') === 'All*,Images,Videos,Articles'));
+ check('Notes / Conversations / Images / Videos / Articles sit under the chips, Notes on', await page.evaluate(() =>
+ [...document.querySelectorAll('.media-mode')].map((b) => b.textContent + (b.classList.contains('on') ? '*' : '')).join(',') === 'Notes*,Conversations,Images,Videos,Articles'));
console.log('\n[Images: a grid]');
await mode('images');