intake form experiences update #58
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Ryan Gunawan <[email protected]> Co-authored-by: Teresa Yu <[email protected]>
…ing hardcoded options Co-authored-by: Ryan Gunawan <[email protected]>
…s sorted by id ascending, pass complete props to LovedOneForm
…intake_form_processor, delete related table columns
test_intake_form_processor.py
…ettier Co-authored-by: Ryan Gunawan <[email protected]> Co-authored-by: Teresa Yu <[email protected]>
…in loved_experiences
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notion ticket link
Intake Form Experiences Update
Implementation description
Add a scope enum column to experiences (patient, caregiver, both, none), wiping existing entries for consistency.
Update the seeder to include experiences with scopes; treatments seeder stays as-is.
Create a new API endpoint to return filtered experiences (by target) and all treatments.
Update frontend forms to fetch options from the API instead of hardcoded constants.
Remove all "Other" treatment/experience fields in forms, interfaces, and backend processing.
Update or add tests to cover API changes and remove “other” field logic.
Steps to test
What should reviewers focus on?
Checklist