-
Notifications
You must be signed in to change notification settings - Fork 824
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
fix: pull issue with multi-env notifications #6475 #6525
Conversation
- fix notificaiton category multi-env handling - fix to ask for `API key` for FCM on `remove notification` command - add E2E for notification testing
Codecov Report
@@ Coverage Diff @@
## master #6525 +/- ##
==========================================
- Coverage 56.84% 56.42% -0.43%
==========================================
Files 487 430 -57
Lines 22076 21124 -952
Branches 4414 4233 -181
==========================================
- Hits 12550 11919 -631
+ Misses 8649 8393 -256
+ Partials 877 812 -65
Continue to review full report at Codecov.
|
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.
💯 for adding an e2e
This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Issue #, if available:
#6475
Description of changes:
API key
for FCM onremove notification
commandBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.