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

Example screener from all 3 current library benefits and a fake benefit

Closed
  • Is something wrong?
#525 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
backend, developer-experience

Research direction

Start by locating the automatically imported example screener and the current OOPA, SCTF, and Homestead library benefits. Build the new screener independently, adding Philly Cash with its stated criteria, helpful description comments, and DMN annotations. Verify that a new user receives it and exercise the web app functions represented by the example.

Written by the indexing model from the issue text.

Description

Let's replace the current (incomplete) example screener (the screener that is automatically imported to new user accounts) with a new one that screens for the current 3 library benefits (OOPA, SCTF, Homestead) plus a fake custom benefit called "Philly Cash" (where the only criteria is that you live in Philadelphia and you would like extra cash).

Build the screener from scratch rather than referencing the existing screener/checks/etc.

Try to exercise all functions of the web app with the example screener and include helpful comments in description fields and annotations on DMN for custom checks, etc. with the goal of orienting new users of the app as much as possible. (be creative!)

Dominant language
Java
Stars
16
Forks
5
Avg merge
14h 45m
Merged PRs (30d)
25

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • 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 CodeForPhilly/benefit-decision-toolkit

All issues in CodeForPhilly/benefit-decision-toolkit

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.