Don't show library benefits in picker that have already been added to the screener
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- java
- Domain
- full-stack
Research direction
Find the library benefit picker and the screener state that tracks benefits already added. Start by locating the picker entry point and how it loads the selected benefits; filter out benefits already present in the screener. Done when added benefits no longer appear in the picker while benefits not yet added remain available.
Written by the indexing model from the issue text.
Description
- when adding a library benefit, we shouldn't see any of the benefits that have already been added to the screener
- Dominant language
- Java
- Stars
- 16
- Forks
- 5
- Avg merge
- 16h 37m
- Merged PRs (30d)
- 20
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
CodeForPhilly/benefit-decision-toolkit#565 ·
Maintainers usually reply within 1 day
-
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
-
backend frontend
Difficulty 5/5 Over a week Newbie friendliness 35/100
CodeForPhilly/benefit-decision-toolkit#569 ·
Maintainers usually reply within 1 day
All issues in CodeForPhilly/benefit-decision-toolkit
Similar issues
-
human-required sync-failed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/osdu-spi-file#63 ·
Maintainers usually reply within 1 day
-
approved
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
checkstyle/checkstyle#22129 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Add Hardcharger JDBC driverPossibly taken @prmoore77 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
objectionary/lints#1577 ·
Maintainers usually reply within 2 days