Files
EventSnap/frontend/src/lib
fabi e79e020566 feat(eventsnap): UX review batch-3 — feed virtualization, a11y/UX fixes, shared primitives
Frontend
- Feed: DOM-windowing via @tanstack/svelte-virtual (new VirtualFeed). The window
  virtualizer keeps the sticky header, pull-to-refresh, infinite-scroll sentinel and
  bottom nav working. List = dynamic measured heights keyed by upload id +
  anchorTo:start so an SSE prepend doesn't jump a scrolled reader; grid = measured
  square rows. Drops the content-visibility band-aid and the old FeedGrid.
  measureElement(null) on row unmount prevents ResizeObserver retention; stable
  option callbacks + guarded setOptions avoid O(n) re-measure on like/comment patches.
- Global: viewport-fit=cover (activates safe-area insets), lang=de, PWA manifest +
  maskable icon + apple-touch metas, prefers-reduced-motion, safe-area-top headers.
- Feed reactivity: like/comment SSE patch the single card in place; upload-processed
  debounced in-place merge; IntersectionObserver leak fixed; shared 60s clock.
- CLS: list cards reserve the skeleton aspect box.
- Destructive actions (promote/demote/unban, gallery release) routed through
  ConfirmSheet (host + admin).
- Export OOM: streamed download via single-use ticket instead of res.blob().
- Shared primitives: IconButton (44px hit area), scrollLock action; UploadSheet a11y.
- Polish: api timeout + non-JSON guard, focus-trap offsetParent fix, pull-to-refresh
  passive:false + guards, diashow keyboard a11y, Toaster assertive errors, dark-mode
  gaps, aria-pressed on like/chip state, CameraCapture mic-on-video + retry,
  ConfirmSheet spinner, upload beforeunload warning, emoji->SVG icons.

Backend
- social.rs: like/comment SSE broadcasts now carry the fresh count so feed clients
  patch one card in place instead of refetching page 1.
- admin.rs / main.rs: supporting changes for the above.

Verified: svelte-check 0 errors, frontend build clean, /feed SSR 200. Runtime feed
scroll-feel validation still owed (documented in FOLLOWUPS.md).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-30 19:16:48 +02:00
..

lib/ conventions

Short rules. The patterns we already follow as of v0.16 — write new code that fits.

One store per cross-cutting concern. A single *-store.ts file owns each one:

  • auth.ts — JWT / PIN in localStorage, isAuthenticated writable
  • ui-store.ts — bottom-nav visibility, upload-sheet open state, FAB badge count
  • data-mode-store.ts — Saver vs Original media-loading preference
  • privacy-note-store.ts — admin-configured Datenschutzhinweis text
  • quota-store.ts — live per-user storage snapshot
  • upload-queue.ts — IndexedDB-persisted upload queue + processing state

Don't import these into other stores unless strictly necessary; let pages compose them.

DTOs mirror Rust types. All TS interfaces live in types.ts. Each one carries a // mirrors backend/src/path::TypeName comment so the two stay searchable. If you add a Rust DTO, add the TS twin in the same PR.

Gestures via Svelte actions in actions/. Long-press, double-tap, future swipe — each is a use: action that fires a CustomEvent. Components stay free of gesture plumbing.

Reusable bottom sheets via ContextSheet.svelte. Pass an actions: ContextAction[] array. Any page that needs a long-press / kebab context menu uses the same primitive.

SSE relays are listed in sse.ts::KNOWN_EVENTS. New server event → add one entry to that array, that's it.

Diashow transitions live in diashow/transitions/. Each is a Svelte component plus one entry in transitions/index.ts. Adding a new animation is two-line work; no diashow code needs to change.

No new global stores beyond the list above unless the new concept is genuinely app-wide. Page state belongs in the page.