Registration API Update - #3641
Merged
Merged
Conversation
- change MeetingRegistration.reg_type field to hold only one type - allow multiple MeetingRegistration records per person/meeting (one for each reg_type)
Member
|
We may want consider a feat branch for this that brings the new meeting attendance api in at the same time. |
Financialcare
approved these changes
Mar 18, 2022
rjsparks
marked this pull request as draft
March 21, 2022 19:21
Financialcare
approved these changes
Apr 19, 2022
1 task
rpcross
marked this pull request as ready for review
June 16, 2022 19:57
rjsparks
approved these changes
Jun 16, 2022
Member
|
Failing test is unrelated. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
(one for each reg_type)