Testing: unit tests for the favicon helpers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- testing
Research direction
Read lib/icons/favicon.ts and check the existing Vitest setup and nearby test conventions. Add tests for faviconHtml, webManifest and faviconStyle, covering each acceptance criterion. Run pnpm test; the work is done when the tests cover those behaviors and the command passes.
Written by the indexing model from the issue text.
Description
Summary
Add Vitest tests for lib/icons/favicon.ts (faviconHtml, webManifest, faviconStyle).
Where to look
lib/icons/favicon.ts
Acceptance criteria
-
faviconHtmllists every icon file with the rightrel,sizesandtype. -
webManifestis valid JSON with the brand name and theme color. -
faviconStylefalls back to the given color when the style has none. -
pnpm testpasses.
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. 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
- 6h 32m
- Merged PRs (30d)
- 31
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yakew7/DesignHub
-
area: backgrounds difficulty: easy good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area: ui difficulty: easy good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
area: social difficulty: easy enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area: social difficulty: easy enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Docs: write a translation guide for contributorsPossibly taken @Muthulakshmikumar claimed this 3 days ago. Openarea: docs difficulty: easy documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
yakew7/DesignHub#225 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in yakew7/DesignHub
Similar issues
-
documentation good first issue
Difficulty 2/5 Half a day Newbie friendliness 72/100
sujithputta02/Esapay#13 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ehmpathy/rhachet-roles-bhuild#468 ·
Maintainers usually reply within 1 day
-
Share dialog: the address book's contact count reads "1 contacts" (no singular form in any language)Possibly taken @chibenwa claimed this today. Openai-driven-qa bug claude Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
linagora/twake-contacts-frontend#271 · 1 comment ·
Maintainers usually reply within 1 day
-
factory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Koenkk/zigbee2mqtt#33402 ·
Maintainers usually reply within 1 day