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

Explore unifying DMN storage and execution path for custom and library checks

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Domain
full-stack

Research direction

Start by mapping how custom and library checks are created, edited, stored, and used in the web app, then review the constraints of keeping the library as a standalone API. Done would require a decided unified library model, with permissions and sharing differences defined and the DMN editing experience addressed.

Written by the indexing model from the issue text.

Description

big lift refactor

We have complexity arising from the differences in how custom checks and library checks are created, edited, stored, and used in the web app.

Assumption/ideal to explore: All checks should exist under a single "library" paradigm. They should be implemented as similarly as possible and managed via web interface. The difference between "custom" and "library" should come down to permissions and sharing logic.

Advantages:

  • less complexity in the web app's code paths and in the "eligibility check" concept. (one paradigm instead of two)
  • one interface for creating/managing
  • opens up interesting features like sharing checks, duplicating/modifying library checks, promoting custom checks to the library, using existing library checks within a custom check, etc.

Probable challenges:

  • keeping the library usable as a standalone API
  • the difference between how custom and library checks are currently implemented (e.g. more boilerplate and DMN know-how are required for library checks)
  • significant UX challenges to ensure proper editing of checks with guardrails necessary (simplifying or otherwise improving the default DMN-editing experience)
Dominant language
Java
Stars
16
Forks
5
Avg merge
1d 26m
Merged PRs (30d)
25

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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.