Show input constraints on problems
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, next.js, node.js
- Domain
- full-stack, testing
Research direction
Read backend/arena/docs/problems.md and inspect backend/arena/scripts/validate-problems.js, frontend/pages/problems/[slug].js, and frontend/pages/battle.js. Run cd backend && npm run validate:problems to understand the current checks. Done means constraints are documented, checked against test inputs where possible, rendered on both pages, and validation catches a test input that violates a stated bound.
Written by the indexing model from the issue text.
Description
Problems never state input sizes. Players cannot tell whether a quadratic solution is fine or will time out, so they find out by failing hidden tests.
What to do
- Add an optional
constraintsfield to the problem format: a short list of strings such as"1 <= scores.length <= 10^5". Document it inbackend/arena/docs/problems.md. - Extend
backend/arena/scripts/validate-problems.jsto check, where it can, that every test input actually stays inside the stated bounds for simple numeric and length constraints. - Show constraints under the examples wherever the description renders (
frontend/pages/problems/[slug].js,frontend/pages/battle.js). - Add constraints to as many of the 45 problems as you can. Partial coverage across several pull requests is fine.
Definition of done
cd backend && npm run validate:problemspasses, and fails if you add a test that breaks a stated bound.- Constraints render in practice and battles.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No 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 sennaicodes/codearena
-
Add issue and pull request templatesMay be free again @franciscorodr26 claimed this 17 days ago, and no pull request is open. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
sennaicodes/codearena#13 · 1 comment ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
sennaicodes/codearena#34 ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 35/100
sennaicodes/codearena#33 ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
sennaicodes/codearena#32 ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 38/100
sennaicodes/codearena#31 ·
All issues in sennaicodes/codearena
Similar issues
-
Clinic sharing: fast sync refusal message suggests Delete Data, which only developer builds haveOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
avniproject/avni-client#2228 ·
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/open-webui#33196 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fable-compiler/Fable#5157 ·
Maintainers usually reply within 1 day
-
New tool: PaperBananaPossibly taken @github-actions claimed this today. Opensubmission triage
Difficulty 1/5 Under an hour Newbie friendliness 75/100
kausalflow/tools#243 · 1 comment ·
Maintainers usually reply within 1 day
-
area: apple-music area: build-release bug effort: small priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ChristianTabor/Argon#32 ·
Maintainers usually reply within 1 day