-
Notifications
You must be signed in to change notification settings - Fork 13k
fix: Notify user stream when enabling/disabling email2fa #35140
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
Conversation
|
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: ceca6df The changes in this PR will be included in the next version bump. This PR includes changesets to release 35 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #35140 +/- ##
========================================
Coverage 59.43% 59.43%
========================================
Files 2825 2825
Lines 68155 68155
Branches 15123 15123
========================================
Hits 40505 40505
Misses 24992 24992
Partials 2658 2658
Flags with carried forward coverage won't be shown. Click here to find out more. |
MarcosSpessatto
left a comment
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.
What about adding a test to cover this?
dougfabris
left a comment
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.
Approving on behalf of frontend team
Proposed changes (including videos or screenshots)
When a user enables/disables their email two factor, we were not sending this info on the streams, due to which the client side's
Meteor.user()wasn't reactive to this change.This PR propagates this change in user, making the client reactive to this change.
Issue(s)
The email 2FA buttons on user's security page are not reactive.
Steps to test or reproduce
Further comments
CORE-977