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

Add more hard problems

Open
  • Is something wrong?
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, node.js, python
Domain
backend, testing

Research direction

Read backend/arena/docs/problems.md and inspect the existing problem JSON and reference solutions in backend/arena/problems/ and backend/arena/solutions/ to understand the format and constraints. Add one original hard problem with JavaScript and Python reference solutions, using only types listed in issue #3 and keeping the gaming theme. Run cd backend && npm run validate:problems; done means both solutions pass all examples and tests, including edge cases and a large input that rules out brute force.

Written by the indexing model from the issue text.

Description

enhancement help wanted

The problem set has 17 easy, 19 medium and only 9 hard problems. Ranked battles at high ratings draw from the hard pool, so strong players see repeats quickly.

What we need

New hard problems, ideally in topics the set barely covers today: union find, trie, topological sort, sweep line, bit manipulation and two pointers each appear once or twice.

How to add one

  • Read backend/arena/docs/problems.md.
  • Create backend/arena/problems/<id>.json plus two independently written reference solutions, backend/arena/solutions/<id>.js and <id>.py.
  • Keep the gaming theme the rest of the set uses (lobbies, ratings, loot, replays).
  • Use only the types listed in #3 so every language driver can run it.

Definition of done

  • cd backend && npm run validate:problems passes: both references pass every example and test.
  • Tests include edge cases and at least one large input that a brute-force solution would time out on.
  • Problems are your own work, not copied from another site.

One problem per pull request is perfect.

Dominant language
JavaScript
Stars
0
Forks
2
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 sennaicodes/codearena

All issues in sennaicodes/codearena

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.