Skip to content
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

Merged
merged 8 commits into from
Mar 2, 2021
Merged

fix: pull issue with multi-env notifications #6475 #6525

merged 8 commits into from
Mar 2, 2021

Conversation

attilah
Copy link
Contributor

@attilah attilah commented Feb 1, 2021

Issue #, if available:

#6475

Description of changes:

  • fix notification category multi-env handling
  • fix to ask for API key for FCM on remove notification command
  • add E2E for notification testing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

- fix notificaiton category multi-env handling
- fix to ask for `API key` for FCM on `remove notification` command
- add E2E for notification testing
@attilah attilah requested a review from yuth February 1, 2021 17:29
@attilah attilah requested a review from a team as a code owner February 1, 2021 17:29
@attilah attilah linked an issue Feb 1, 2021 that may be closed by this pull request
@codecov
Copy link

codecov bot commented Feb 1, 2021

Codecov Report

Merging #6525 (ffacdad) into master (59d66fe) will decrease coverage by 0.42%.
The diff coverage is 9.75%.

Impacted file tree graph

@@            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     
Impacted Files Coverage Δ
.../amplify-category-notifications/lib/channel-FCM.js 0.00% <0.00%> (ø)
...fy-category-notifications/lib/multi-env-manager.js 0.00% <0.00%> (ø)
...extensions/amplify-helpers/get-frontend-plugins.ts 7.69% <0.00%> (-8.98%) ⬇️
...ackages/amplify-cli/src/init-steps/s9-onFailure.ts 50.00% <ø> (+7.14%) ⬆️
packages/amplify-cli/src/index.ts 42.38% <33.33%> (-1.19%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fd9f50f...ffacdad. Read the comment docs.

Copy link
Contributor

@yuth yuth left a 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

@attilah attilah added this to Review in Bug bash via automation Feb 26, 2021
@yuth yuth moved this from Review to Approved and ready to merge in Bug bash Feb 26, 2021
@attilah attilah merged commit b0803d1 into aws-amplify:master Mar 2, 2021
Bug bash automation moved this from Approved and ready to merge to Done Mar 2, 2021
@github-actions
Copy link

github-actions bot commented Mar 3, 2022

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 *-help channels for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Bug bash
  
Done
3 participants