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

Don't show benefit-specific checks in public checks UI or in library API

Open Beginner friendly
#565 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
backend

Research direction

Start with library-api/src/main/resources/checks/income/loop-income.dmn and find how the library categorizes checks for the public UI and library API. Move checks specific to the LOOP benefit into the internal category, then confirm they no longer appear in either public surface while general income checks remain available.

Written by the indexing model from the issue text.

Description

These are checks that should be in the "internal" category of the library.

Example: library-api/src/main/resources/checks/income/loop-income.dmn should not be in income, it should be in internal because it is specific to the LOOP benefit.

Dominant language
Java
Stars
16
Forks
5
Avg merge
15h 42m
Merged PRs (30d)
21

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.