Restructure user record to have multiple roles #429
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.
Potentially controversial change to how user roles are managed. Expecting this will allow for more flexibility for new admin features and also given the need to support other types of applicants in #386.
Resolves #421. See description of changes for notable modifications besides renaming the field.
Changes
UserRecord
store multiple possible rolesnull
null
could be better to indicate unknown rather than explicitly no roles, but functionally, an empty array is simplercheck_in_participant
confirm_attendance_non_hacker
AfterValidator
forApplicant.roles
to includeRole.APPLICANT
ParticipantAction
: function was used like booleanTesting
Note any older records in the local database will need to be updated.