opensafely-core / opensafely-core/opencodelists
Bulk include/exclude of sections in the builder
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 60
- Forks
- 16
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 17
Description
Why are we doing this?
We want to make it easier for researchers to quickly include or exclude the concepts they need (or don't need) for their codelist.
However, we also want to ensure that researchers are making a deliberate and informed choice about what concepts to include, or not.
How will we know when it's done?
When researchers can quickly include or exclude all concepts within a given section when building a codelist.
What are we doing?
- Adding an option to include or exclude all concepts within a given section. This could be as simple as two text links that say "include all" or "exclude all".
- Adding a dialog for the researcher to confirm the change before it's made. There should be enough information in the dialog box for the researcher to be able to easily make that decision.
- Mention that concepts within the section that have been explicitly included/excluded will be changed too.
- Adding / extending a playwright test to include this functionality (as well as the usual unit tests).
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Locate the builder's section controls and the existing unit and Playwright tests that cover concept inclusion and exclusion. Start by tracing how a section's concepts are currently changed. Done means researchers can include or exclude all concepts in a section, confirm the change with sufficient information, and the behavior is covered by unit and Playwright tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright, python
- Domain
- frontend, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100