Don't show benefit-specific checks in public checks UI or in library API
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
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
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
- 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 CodeForPhilly/benefit-decision-toolkit
-
backend Good for newcomer quick win
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CodeForPhilly/benefit-decision-toolkit#562 ·
Maintainers usually reply within 1 day
-
documentation quick win
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CodeForPhilly/benefit-decision-toolkit#445 ·
Maintainers usually reply within 1 day
-
Make issue templatesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CodeForPhilly/benefit-decision-toolkit#425 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
CodeForPhilly/benefit-decision-toolkit#566 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
CodeForPhilly/benefit-decision-toolkit#564 ·
Maintainers usually reply within 1 day
All issues in CodeForPhilly/benefit-decision-toolkit
Similar issues
-
pdfium-drift
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Stirling-Tools/JPDFium#176 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiero-ledger/hiero-consensus-node#27712 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Vakore/ZappierGames#162 ·
-
Improve README documentation clarity and fix minor wording issuesPossibly taken @simplesilence claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
resilience4j/resilience4j#2567 ·
Maintainers usually reply within 6 days
-
Priority/High
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
wso2/dpdp-accelerator#417 ·
Maintainers usually reply within 1 day