Settings: the ignore list keeps the same app twice in different case
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
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, wherenew Set(...)removes duplicates. Both the settings file and every change from the Settings window go through ittests/settings-color.test.ts: thesanitizeSettingsandisIgnoredApptests
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 testpasses
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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 alexsilver8/openpaste
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
alexsilver8/openpaste#31 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
alexsilver8/openpaste#32 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
alexsilver8/openpaste#30 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
alexsilver8/openpaste#29 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
alexsilver8/openpaste#27 ·
All issues in alexsilver8/openpaste
Similar issues
-
test: make the #3408 Claude OAuth token fixture obviously fake so secret scanners stop flagging itOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#3436 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lingdojo/kana-dojo#32505 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/gh-aw-firewall#10040 ·
Maintainers usually reply within 1 day
-
review-followup
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
griffinwork40/agent-afk#3868 ·
Maintainers usually reply within 1 day
-
area: import-export bug status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
amatya-aditya/obsidian-rss-dashboard#1191 ·
Maintainers usually reply within 1 day