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

Search: accept more type names, like is:colours, is:urls and is:photos

Open Beginner friendly
  • Is something wrong?
#32 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
92/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
electron, react, typescript
Domain
frontend, search

Research direction

Read KIND_ALIASES in src/shared/search.ts and the parseQuery tests in tests/search.test.ts. Add the listed plural and synonym names for their matching types, then check that each alias maps to the expected type. Run pnpm test; done means all listed forms filter correctly and the tests pass.

Written by the indexing model from the issue text.

Description

enhancement good first issue

Search understands a few names for each type, but not always the plural or the obvious synonym:

Works Doesn't work yet
is:colour is:colours
is:url is:urls
is:picture is:pictures, is:photo, is:photos
is:screenshot is:screenshots
is:snippet is:snippets

A name it doesn't know is searched as plain text, so is:colours currently finds nothing at all.

Where to look
  • src/shared/search.ts: KIND_ALIASES. The same names work after type: and kind:
  • tests/search.test.ts: the parseQuery tests

#9 and #10 also change parseQuery. This one only adds to the alias table, so it shouldn't conflict with them.

Done when
  • Every name in the right-hand column filters to its type
  • A test checks each alias in KIND_ALIASES maps to the right type (looping over the table is fine), and pnpm test passes

Suggested pull request title: feat(search): accept more type names like is:colours and is:urls

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
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.