Open
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.
To begin, we need to run the rails db:seed command. This command populates default questions and uploads patient data by calling the fetch user service, which retrieves dummy data from an API to get users.
When a user navigates to the new check-in page, they will see two questions. They can select an option for each question and submit the form. Upon submission, the check-in show page opens with a relevant flash message as specified in task 1.
On the backend, when a user accesses the new check-in page, we initialize a CheckIn object and display all the questions. Once the user selects options for all the questions, we send the question IDs along with the selected option titles to the backend. We save this data using nested attributes. The reason for sending the option titles to the backend is to ensure that any future changes to these options do not affect the responses from previous check-ins.