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
UI/messages #62
Merged
Merged
UI/messages #62
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
Message unit tests not finished.
PSchmiedmayer
approved these changes
Aug 9, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job with the PR; looks great!
1 task
This was
linked to
issues
Aug 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Update Messages UI and Data Structure
♻️ Current situation & Problem
The messages we currently have in the app were implemented before the server structure for messages was finalized, so they are out of date at the moment. For example, they are called
notifications
instead ofmessages
, and there are no actions associated with them at the moment.⚙️ Release Notes
Notification
nomenclature withMessage
MessageManager
to dismiss messages by calling a cloud function instead of writing directly to FirestoreMessage
data structure to comply with Backend Data Structure, includingMessageAction
field toMessage
so that each message potentially has an associated action.Message
to support localized decoding.MedicationDetail
model up to speed with the backend implementation (e.g.DosageInformation
is no longer optional, and we now signal that the patient hasn't started a medication yet by saying "not started" instead of hiding the medication details and relying on the description).The Home Screen dashboard now looks like this:
📚 Documentation
See inline documentation.
✅ Testing
UI tests are completed using mock messages injected directly into the
MessageManager
(i.e. no firebase interactions). A full cycle Unit/UI test that makes sure the decoding functionality works as intended will be completed as soon as #24 is complete.Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: