feat(web): people-specific empty state explains why no persons appear yet #1399
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/people-empty-state-hint"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fresh or small libraries with only a few photos per person never reach the minimum group size for face grouping, so the people page (
/discovery/domains/people) showed the generic "No instances discovered yet" empty state — which reads like a bug.On the people domain (and only there, and only while no search is active) the empty state now explains that faces are grouped into people once enough similar photos exist, and tells the user to add more photos.
EmptyStatecomponent (iconusers); no styling changesddiPeopleEmptyTitle/ddiPeopleEmptyBodyin en/de/da (household wording per spec 007: no clustering/discovery/instance terminology)Verification: JSON parity of all three bundles (2599 keys each),
npm run checkin apps/web — 0 errors, only pre-existing warnings; no manual version bump (pipeline-computed).