generated from StanfordSpezi/SpeziTemplateApplication
-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Firebase Cloud Code #24
Closed
Closed
Conversation
This file contains 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
pauljohanneskraft
added
good first issue
Good for newcomers
enhancement
New feature or request
dependencies
Pull requests that update a dependency file
and removed
good first issue
Good for newcomers
labels
Aug 5, 2024
This was referenced Aug 5, 2024
Merged
PSchmiedmayer
pushed a commit
that referenced
this pull request
Aug 9, 2024
# Add Symptoms Questionnaires as a Message Action ## ♻️ Current situation & Problem Currently, we do not have a way for the user to take their bi-weekly symptom survey (the "Complete Questionnaire" action did not do anything). ## ⚙️ Release Notes - Implemented a Questionnaire Sheet View that pops up when the user taps the "Complete Questionnaire" message that fetches and displays the questionnaire associated with the message (KCCQ-12 survey). - On completion, saves the user's response to the user's quesitonnaireResponses collection. ## 📚 Documentation NA ## ✅ Testing UI tests confirm that the message action triggers the appearance of a sheet that displays a questionnaire. At the moment, the questionnaire displayed is a default testing questionnaire provided by `FHIRQuestionnaire`. We can only test the fetching operations once #24 is complete. ### Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordBDHG/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordBDHG/.github/blob/main/CONTRIBUTING.md): - [X] I agree to follow the [Code of Conduct](https://github.com/StanfordBDHG/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordBDHG/.github/blob/main/CONTRIBUTING.md).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Remove Firebase Cloud Code
♻️ Current situation & Problem
Currently, this repository contains code that is solely used for Firebase Cloud functionality. We get rid of it here, so that it can thrive in the ENGAGE-HF-Firebase repository.
⚙️ Release Notes
Moving Firebase Cloud code to a new repository.
📚 Documentation
No documentation needed.
✅ Testing
For testing the iOS code in conjunction with the Firebase Cloud Functions, we will need to figure out a way to clone and run the other repository as part of the testing run of the iOS application.
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: