Add private_data field to ExtraUserDetail #4528
Merged
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.
Checklist
Description
Added 'private_data' field to the extra user detail model.
Notes
There are some properties that need to be set on the User but not editable/viewable from the
/me
endpoint. As a concrete example, for mass emails, we use a boolean inextra_details
to store whether a particular email has been sent to a user. We don't want users to be able to unset that boolean, because it might result in them getting sent the same email twice.