Storage: clear the icon cache from the panel

Open
  • Is something wrong?
#511 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
66/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
databases, frontend

Research direction

Start with the storage summary in components/projects/storage-panel.tsx and lib/storage-report.ts, then the icons table in lib/db.ts. Add a button that reports the row count and size, then deletes only the icons rows, leaving projects, versions and settings alone. Add en, es, fr and hi strings, and an end-to-end test that caches an icon, clears the cache and checks the count is zero. Done when that test passes and docs/storage.md describes the button.

Written by the indexing model from the issue text.

Description

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

Summary

The panel shows how many icons are cached and how big that is, but the only way to clear them is to clear all site data. Add Clear the icon cache, which empties the icons table and nothing else, with an undo that is not needed because the icons are fetched again when used.

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

Where to look

  • components/projects/storage-panel.tsx and lib/storage-report.ts
  • lib/db.ts (the icons table)
  • docs/storage.md

Behaviour

  • Add a button that deletes the rows of icons, after saying how many and how much space that frees.
  • Leave projects, versions and settings alone, and say so.
  • Translate the text in en, es, fr and hi.

Acceptance criteria

  • An end-to-end test caches an icon, clears the cache and sees the count go to zero with the projects intact.
  • The Icon Studio still works offline for icons fetched again later.
  • docs/storage.md and the troubleshooting guide mention 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 23m
Merged PRs (30d)
74

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.