Store the opt-in user details in the options#85
Merged
Conversation
This will help provide a point of reference if the user opt-in needs to be sent again or we need it for some other purpose down the road.
ChrisMKindred
approved these changes
Sep 14, 2023
Contributor
ChrisMKindred
left a comment
ChrisMKindred
left a comment
There was a problem hiding this comment.
This will be very helpful in the future.
This file contains hidden or 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
2 participants
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 will help provide a point of reference if the user opt-in needs to be sent again or we need it for some other purpose down the road.
For reference, the value stored in the database is the same json-encoded payload sent to the server during user opt-in:
{ "name":"admin", "email":"admin@telemetry-library.lndo.site", "plugin_slug":"telemetry-library" }