Premium downgrade new ping #1643
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses MPP-1003.
New feature description
All this PR does is add a ping within the
_update_all_datafunction which is called via the_handle_fxa_profile_changefunction. The new ping is identified by the event nameuser_has_downgradedand is triggered if the user is no longer a premium user, but they had premium and now does not have premium.Screenshot (if applicable)
Not applicable.
How to test
We should have a test user that has a subscription - have that user cancel the subscription.
Checklist
/static/scss/libs/protocol/css/includes/tokens/dist/index.scss).