Offline: keep the studios a person uses most for offline use on their own, with a switch

Aperta
  • Qualcosa non va?
#540 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
57/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
nextjs, typescript

Direzione di ricerca

Start with scripts/service-worker-source.mjs and trace how rekeep and rememberRoute handle offline storage; then read store/command-recents-store.ts, store/nav-store.ts, and components/projects/storage-body.tsx for recents and the Offline use controls. Check existing tests for service worker storage and settings, then add coverage for the option off and on. Done means the remembered, translated switch defaults on, only keeps up to four recently used studios within the existing size cap, and the two named docs explain the behavior.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: ui difficulty: medium enhancement help wanted v2.0.0

Summary

A studio is kept when it is opened online, or by choosing it in the Storage panel. A person who always works in three studios could have those kept again after every update with no step, and have a switch to turn it off.

Part of the 2.0.0 plan: fewer, better and fully tested studios, on a calmer and faster site.

Where to look

  • scripts/service-worker-source.mjs (rekeep, rememberRoute)
  • store/command-recents-store.ts and store/nav-store.ts
  • components/projects/storage-body.tsx (Offline use)

Behaviour

  • Add an option, on by default, to keep the last four studios used (from the recents) on the next visit online, within the same size cap.
  • Show it as a switch in Offline use and say what it does in one line.
  • Never download a studio that was not used.

Acceptance criteria

  • A test with the option off downloads nothing new, and with it on keeps the recent studios.
  • The option is remembered after a reload and translated.
  • docs/storage.md and docs/troubleshooting.md describe it.

Getting started: fork the repo, then pnpm install and pnpm dev (Node 22+, pnpm 11, no API keys). Before opening a PR, run pnpm typecheck && pnpm test && pnpm lint && pnpm format:check && pnpm check:dashes && pnpm build (CI fails on unformatted files, so pnpm format first). See CONTRIBUTING.md and the first contribution walkthrough.

Everything needed is in the repository. This doesn't need maintainer access, secrets or paid services. Comment below to claim it, and ask questions here any time.

Lingua principale
TypeScript
Stelle
11
Fork
3
Merge medio
6h 9m
PR unite (30g)
73

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di yakew7/DesignHub

Tutte le issue di yakew7/DesignHub

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.