Storage panel: say when the studios were kept again after an update

Open
  • Is something wrong?
#519 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
next.js, typescript
Domain
accessibility, frontend, internationalization, mobile-dev, testing

Research direction

Start with scripts/service-worker-source.mjs at rekeep, then trace messages through components/pwa/pwa-register.tsx and hooks/use-kept-studios.ts to the Storage panel in components/projects/storage-panel.tsx. Run the update end-to-end test first; add coverage for the completion message and list refresh, then verify the translated, screen-reader-announced toast, the no-kept-studios case, and the troubleshooting documentation.

Written by the indexing model from the issue text.

Description

area: projects difficulty: easy enhancement good first issue help wanted v2.0.0

Summary

A new build now downloads again the studios that were kept, in the background, but nothing says it has finished. A person offline soon after an update cannot tell which studios are safe.

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)
  • components/pwa/pwa-register.tsx and hooks/use-kept-studios.ts
  • components/projects/storage-panel.tsx (Offline use)

Behaviour

  • Have the worker post a message to its pages when rekeep ends, with how many studios were kept.
  • Show a short toast, and refresh the kept list in the Storage panel.
  • Say nothing when no studio was kept before the update.

Acceptance criteria

  • The update end-to-end test sees the message.
  • The toast is announced to a screen reader and is translated in all four languages.
  • docs/troubleshooting.md mentions 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.

Dominant language
TypeScript
Stars
11
Forks
3
Avg merge
5h 44m
Merged PRs (30d)
72

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yakew7/DesignHub

All issues in yakew7/DesignHub

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.