3dtours/RecipesCam
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

api+admin: let the curator take a photo off the landing, not just move it

Browse Source 
Uploads still land in the community strip with consent on, by the uploader's own
tick — that default stays. What was missing is the curator's removal: the slot
select only offered the other three live placements, so "off the strip" meant
publishing the photo somewhere else or deleting the uploader's row.

`off` is a fifth slot value. The reel draws slot === 'strip' and each live slot
draws its own, so an `off` photo renders nowhere on the landing, while its owner
still has it in MY PHOTOS.
This commit is contained in:
3dtours
2026-09-18 15:07:04 +07:00
parent dcea6b926f
commit 97836fde8a
6 changed files with 26 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docker/backend/test/security.mjs
+10
View File
@@ -304,6 +304,16 @@ try {
'the slot is public, the owner is not',
((await actor().req('/photos')).body?.photos ?? []).find((r) => r.id === id)?.slot === 'qr',
);
// `off` is the curator's removal: the reel draws slot === 'strip' and the
// live slots draw their own, so the row shows up nowhere — but the uploader
// keeps it in their folder.
const off = await patch(`/admin/photos/${id}`, { slot: 'off' });
check('an admin takes a photo off the landing', off.status === 200 && off.body?.slot === 'off', JSON.stringify(off.body));
check(
'an off photo is on no landing slot',
((await actor().req('/photos')).body?.photos ?? []).find((r) => r.id === id)?.slot === 'off',
);
check('its owner still has it in the folder', ((await user.req('/photos/mine')).body?.photos ?? []).some((p) => p.id === id));
check('an unknown slot is refused', (await patch(`/admin/photos/${id}`, { slot: 'nope' })).status === 400);
check('placing an unknown photo is a 404', (await patch('/admin/photos/999999', { slot: 'qr' })).status === 404);