-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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.
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
fix: scheduleId to work on PATCH event type host assignment via api v1 #19546
fix: scheduleId to work on PATCH event type host assignment via api v1 #19546
Conversation
@Shpadoinkle is attempting to deploy a commit to the cal Team on Vercel. A member of the Team first needs to authorize it. |
f946426
to
ea3547c
Compare
Graphite Automations"Add consumer team as reviewer" took an action on this PR • (02/26/25)1 reviewer was added to this PR based on Keith Williams's automation. "Add community label" took an action on this PR • (02/26/25)1 label was added to this PR based on Keith Williams's automation. "Add ready-for-e2e label" took an action on this PR • (03/03/25)1 label was added to this PR based on Keith Williams's automation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a split from the other PR, so is this part done?
@retrogtx this pr is separate, and does not require the other pr to be merged first. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
E2E results are ready! |
calcom#19546) Co-authored-by: amrit <iamamrit27@gmail.com>
What does this PR do?
Updates to api V1:
hosts
via the apiMandatory Tasks (DO NOT REMOVE)
How should this be tested?
Using the calcom frontend, set up a host on a Round robin using a custom schedule other than their default.
If you use the patch endpoint to set a host, passing in
scheduleId
using the current api is ignored. and the hosts will use their default scheduleIf you use the patch endpoint using this change, then passing in a scheduleId will save it as expected