Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Registration API Bug: switching reg type results in multiple MeetingRegistration records #7608

Open
1 task done
rpcross opened this issue Jun 28, 2024 · 1 comment
Open
1 task done

Registration API Bug: switching reg type results in multiple MeetingRegistration records #7608

rpcross opened this issue Jun 28, 2024 · 1 comment
Labels
accepted bug Something isn't working component: meeting/ major

Comments

@rpcross
Copy link
Collaborator

rpcross commented Jun 28, 2024

Describe the issue

If a registrant switches registration type onsite -> remote, or vice-versa, a new MeetingRegistration record is created, resulting in two records for the person. The question is, how do we differentiate this scenario, switching registrations, from the, albeit rare, situation where someone does actually register for both online and remote.

Code of Conduct
@rpcross rpcross added the bug Something isn't working label Jun 28, 2024
@rjsparks
Copy link
Member

the post could show the entire correct state for the Person, then the api handler would know what to do.

rpcross added a commit to rpcross/datatracker that referenced this issue Jul 21, 2024
@rpcross
fix: refactor api_new_meeting_registration. Fixes ietf-tools#7608
a56439f 
- change to use JSON payload
- handle multiple records in one request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepted bug Something isn't working component: meeting/ major
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rjsparks @rpcross