Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Settings: the ignore list keeps the same app twice in different case

Open Beginner friendly
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
electron, typescript
Domain
desktop

Research direction

Start in src/shared/settings.ts at sanitizeSettings, then review the related sanitizeSettings and isIgnoredApp tests in tests/settings-color.test.ts. Add a test with app names that differ only in case and verify the first spelling and list order are preserved. Done means the test passes and pnpm test passes.

Written by the indexing model from the issue text.

Description

bug good first issue

The ignore list matches app names without regard to case, but adding an app doesn't check case. Adding 1password while 1Password is on the list adds a second chip:

sanitizeSettings({ ignoredApps: [...DEFAULT_IGNORED_APPS, '1password'] }).ignoredApps
// [..., 'Proton Pass', 'Passwords', '1password']

It removes exact duplicates and extra spaces already (' Bitwarden ' disappears), just not ones that differ in case.

Where to look
  • src/shared/settings.ts: sanitizeSettings, where new Set(...) removes duplicates. Both the settings file and every change from the Settings window go through it
  • tests/settings-color.test.ts: the sanitizeSettings and isIgnoredApp tests
Done when
  • Names that differ only in case are kept once, with the spelling that came first
  • The order of the list is otherwise unchanged
  • A test covers it, and pnpm test passes

Adding an app that's already on the list then just clears the field in Settings, which is fine.

Suggested pull request title: fix(settings): keep each ignored app once, whatever its case


New to OpenPaste? CONTRIBUTING.md covers setup, the code conventions and the checks to run before a pull request (pnpm typecheck, pnpm test, pnpm format, pnpm cleaner). Leave a comment if you're picking this up so nobody doubles up.


Generated by Claude Code

Dominant language
TypeScript
Stars
0
Forks
3
PR merge metrics
No merged PRs in 30d

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 alexsilver8/openpaste

All issues in alexsilver8/openpaste

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.