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

Remaining input checks: checkPage screenId, receipt counts, and verdict versus exit code

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
playwright, typescript
Domain
backend, cli, testing-qa

Research direction

Start by locating checkPage, the receipt store's isReceipt, and the stdin Result checks used by usabl comment and usabl enforce; inspect their existing input validation and tests. Cover the shared screenId grammar, whole non-negative receipt counts, and verdict consistency with exit code, with refusals that identify the field without echoing its value. Done when each invalid input is refused and the command line exits 4.

Written by the indexing model from the issue text.

Description

area: engine bug

Three small gaps left after the library boundary checks:

  1. checkPage does not check the caller's screenId against the shared id grammar. Every other entry point now does.
  2. The receipt store's isReceipt accepts any number for its counts. Counts should be whole, non-negative numbers.
  3. The Result check that usabl comment and usabl enforce run on stdin checks shape only. A Result whose verdict disagrees with its exit code is accepted.

Each one should refuse with InputRefusedError (or exit 4 on the command line), naming the field and never echoing the value.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
2h 48m
Merged PRs (30d)
8

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 usabl-dev/usabl

All issues in usabl-dev/usabl

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.