-
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
Feature: Patient notifications #228
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #228 +/- ##
========================================
Coverage 72.22% 72.22%
========================================
Files 3 3
Lines 18 18
Branches 3 3
========================================
Hits 13 13
Misses 5 5 ☔ View full report in Codecov by Sentry. |
59a701c
to
6891d27
Compare
6891d27
to
d2405c8
Compare
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
13077695 | Triggered | Stream Keys | 8f69704 | eas.json | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
3e292ae
to
8696017
Compare
8696017
to
f8316e9
Compare
f8316e9
to
f735981
Compare
*ft(booking):add FlutteWave payment method *ft: allow user to end chats and leave a review *ft: patient notification context *feature: populate initial notifications and add new ones upon being added to the db *ft: fetched notifications and reworked on the notifications screen and notification Listing component *fix: device notification on notification creation *rf: refactored some erros *ft(notifications):add logic to insert notifications on every key action *ft(notifications):add logic to insert notifications on every booking
f735981
to
8f69704
Compare
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.
good job
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.
LGTM
What does this Pull Request do?
Allows the user to receive realtime notifications about different occurrences or actions
Description