fix: hide privacy policy toast during onboarding, and for onboarded users#25217
fix: hide privacy policy toast during onboarding, and for onboarded users#25217
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
…into jb-privacy-policy-hotfix
…sk-extension into jb-privacy-policy-hotfix
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #25217 +/- ##
===========================================
+ Coverage 65.65% 65.66% +0.01%
===========================================
Files 1368 1368
Lines 54271 54301 +30
Branches 14192 14200 +8
===========================================
+ Hits 35627 35652 +25
- Misses 18644 18649 +5 ☔ View full report in Codecov by Sentry. |
Builds ready [0268bea]
Page Load Metrics (552 ± 421 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
|
Great work ! is it posible to add an e2e test for this ? |
| const isFromReminder = new URLSearchParams(search).get('isFromReminder'); | ||
| const trackEvent = useContext(MetaMetricsContext); | ||
|
|
||
| useEffect(() => { |
There was a problem hiding this comment.
can we add a comment on the top of this use effect to explain why we have it here ?
| }; | ||
| } | ||
|
|
||
| export function setOnboardingDate() { |
There was a problem hiding this comment.
is it possible to add a unit test for this function on the action.test.js ? should be sample but better for the test coverage
|
I haven't seen a toast appear yet when following the steps in Edit: Maybe i just need to pick a better dummy date to satisfy |
bergeron
left a comment
There was a problem hiding this comment.
Ok with some minor code edits i think ive reproduced all the cases correctly
|
No release label on PR. Adding release label release-12.2.0 on PR, as PR was added to branch 12.2.0 when release was cut. |
Description
Fixes two bugs:
Related issues
Fixes:
Manual testing steps
New user onbaording after the date:
New user onboarding before the date:
Old user after the privacy policy date:
onboardingDateisnullin the redux state (this simulates a user who has registered before this PR has been in production)Old user before the privacy policy date:
onboardingDateisnullin the redux state (this simulates a user who has registered before this PR has been in production)TL;DR: If the privacy policy date is in the future, the user should never see it -BUT- if the privacy policy is in the past, the user should see it, as long as the user onboarded before the privacy policy date.
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist