docs(supabase): DEV acceptance run, RESP-01 and AVATAR-01 recorded
This commit is contained in:
1 parent
a70166ea11
commit
8c8478c052
4 files changed
+31
-2
No files matched your search
@@ -260,7 +260,15 @@ token, no user content.
|
||||
4. Poll the own row every 1 s, 30 s at most: `clean` → download
|
||||
`object_key` (`storage.from('avatars').download`), keep a blob URL in the
|
||||
auth store; `rejected` → message per code; still `uploaded` after 30 s →
|
||||
"processing, come back later" (the next mount polls again).
|
||||
"processing, come back later" (the next mount polls again). Only a row
|
||||
the section knows at mount resumes: after a full page reload the section
|
||||
mounts before the auth store has read the rows, so it shows the clean
|
||||
photo with « Modifier » and « Supprimer » enabled, and a new save
|
||||
supersedes the waiting row (`deleted`, keys enqueued). An in-app return to
|
||||
Mon compte resumes the polling. Without a running worker (a DEV stack where
|
||||
`docker compose --profile worker up worker` was not started, §3.2 of
|
||||
SUPABASE.md) every new photo stays `uploaded` and ends on that message;
|
||||
the clean photo is kept (AVATAR-01, 2026-10-27, isolated reproduction).
|
||||
5. "Supprimer la photo": confirmation dialog → `remove_avatar()` → monogram.
|
||||
|
||||
Closed failure kinds the UI phrases (`AssetFailure.kind`): `too_large`,
|
||||
|
||||
Reference in new issue
Block a user