-
Notifications
You must be signed in to change notification settings - Fork 11.6k
feat: allow email invites in team event-type assignment #26957
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
base: main
Are you sure you want to change the base?
feat: allow email invites in team event-type assignment #26957
Conversation
- Update CheckedTeamSelect to use CreatableSelect for email input - Add email validation and comma-separated email parsing - Add isEmailInvite and email fields to Host and CheckedSelectOption types - Pass allowEmailInvites prop through AddMembersWithSwitch - Enable email invites in EventTeamAssignmentTab for both fixed and round-robin hosts Closes calcom#13532
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.
3 issues found across 4 files
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="apps/web/modules/event-types/components/tabs/assignment/EventTeamAssignmentTab.tsx">
<violation number="1" location="apps/web/modules/event-types/components/tabs/assignment/EventTeamAssignmentTab.tsx:231">
P2: Email invite hosts all use userId=0, but updatedHosts matches only on userId, causing later email invites to reuse the first invite’s groupId/scheduleId</violation>
</file>
<file name="apps/web/modules/event-types/components/CheckedTeamSelect.tsx">
<violation number="1" location="apps/web/modules/event-types/components/CheckedTeamSelect.tsx:109">
P2: Duplicate emails in a single comma-separated input aren’t deduped, allowing identical invite entries to be added in one create action.</violation>
<violation number="2" location="apps/web/modules/event-types/components/CheckedTeamSelect.tsx:148">
P1: React-select props from callers (e.g., isOptionDisabled, controlShouldRenderValue) are no longer forwarded, causing regressions like allowing disabled options to be selected.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
apps/web/modules/event-types/components/tabs/assignment/EventTeamAssignmentTab.tsx
Show resolved
Hide resolved
- Forward caller props to CreatableSelect (isOptionDisabled, etc.) - Dedupe emails in comma-separated input - Fix userId=0 collision by matching email invites by email
|
@cubic-dev-ai please re-review |
@yuvrajangadsingh I have started the AI code review. It will take a few minutes to complete. |
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.
No issues found across 4 files
Summary
Changes
CheckedTeamSelectto useCreatableSelectfor email inputisEmailInviteandemailfields toHostandCheckedSelectOptiontypesallowEmailInvitesprop throughAddMembersWithSwitchcomponent chainEventTeamAssignmentTabfor both fixed and round-robin hostsTest plan
Closes #13532
/claim #13532