rubyforgood / rubyforgood/alongwithyou
Chronic Conditions — add/edit/delete list
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
Description
Standing diagnoses the patient lives with. Repeatable-entry list, plain rather
than dated — the condition is a standing fact even though episodes are not.
Fields — need confirming, not sourced from any ADR
- Condition
- Diagnosed (approximate date, free text — "around 2019" has to be enterable)
- Treating provider
- Notes
Do not require a precise date. People do not remember them, and a date picker
that will not accept "some time in 2019" is a cognitive-load failure.
Acceptance Criteria
- Add, edit, delete against the encrypted local database
- Built on the #49 component
- Ships its migration
- Approximate dates are enterable without a precise day
- Field list confirmed before merge
- WCAG-aligned; copy neutral per 0004
- Covered by unit tests
Additional Info and Resources
- Not blocked on #118 finishing — only on its props contract. The repository
config, the migration and their tests can be written first against the
in-memory SQLite harness; the screen fills in behind once #118 publishes the
component's shape. - Coordinate your migration id before you start.
assertWellFormedrequires
them contiguous from 1, so parallel PRs each adding "migration 1" all conflict
after the first one merges. Renumbering an unmerged entry is fine — the "never
edit a merged entry" rule only applies once it has shipped. - If "treating provider" should link to a #36 entry rather than be free text, that is a relational feature the repository layer does not have. Free text is the right call for Phase 1 — note the limitation rather than building joins
QA
- Enter a condition with a vague date, relaunch, confirm it persists as typed
- VoiceOver/TalkBack through add, edit and delete
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
Start with the #49 component contract and the in-memory SQLite harness; review assertWellFormed and coordinate the next contiguous migration id. Confirm the field list before implementation, then cover add, edit, delete, vague-date persistence after relaunch, and VoiceOver/TalkBack flows with unit tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite, typescript
- Domain
- accessibility, databases, mobile, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100