feat: implement dynamic database and routing logic#107
Open
thekhushbooyadav1 wants to merge 1 commit into
Open
feat: implement dynamic database and routing logic#107thekhushbooyadav1 wants to merge 1 commit into
thekhushbooyadav1 wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Title: Feat: Implement Remedy Wizard logic and database structure
Description:
This PR introduces the core logic for the Remedy Wizard feature. It implements a robust master database structure and dynamic routing logic to provide personalized remedy suggestions based on user inputs like allergies and age.
Key Changes:
Defined the masterDb object for structured remedy storage.
Implemented submitAssessment logic to handle allergy and age-based filtering.
Set up the foundational routing mechanism for the wizard.
Testing Done:
Verified the routing logic with various age and allergy permutations.
Ensured the masterDb structure is correctly accessible by the component.
Note:
I have followed an atomic commit strategy for this feature to ensure clear project history.