* feat: extract tRPC verification logic to platform libraries and create v2 atoms endpoints
- Extract verifyCodeUnAuthenticated, verifyCodeAuthenticated, and sendVerifyEmailCode logic from tRPC handlers into reusable platform library functions
- Create VerificationAtomsService and AtomsVerificationController following atoms pattern
- Add v2 endpoints: /atoms/verification/email/send-code, /atoms/verification/email/verify-code, /atoms/verification/email/verify-code-authenticated
- Update useVerifyEmail and useVerifyCode hooks to use new v2 endpoints instead of verified-resources endpoints
- Export verification functions from @calcom/platform-libraries following getPublicEvent pattern
- Integrate platform-specific verification hooks into BookerPlatformWrapper
Co-Authored-By: somay@cal.com <somaychauhan98@gmail.com>
* feat: update platform hooks to use v2 verification endpoints
- Update useVerifyEmail hook to use correct response type for v2 endpoint
- Update useVerifyCode hook to use v2 verification endpoint
- All verification functions now properly exported from platform libraries
- Type checking passes with no errors
Co-Authored-By: somay@cal.com <somaychauhan98@gmail.com>
* fix: update v2 API to use workspace version of platform-libraries
- Change package.json dependency from pinned version to workspace version
- Add proper error handling to verification service with NestJS HTTP exceptions
- Convert generic Error objects to BadRequestException and UnauthorizedException
- Ensure verification endpoints return proper HTTP status codes instead of 500 errors
Co-Authored-By: somay@cal.com <somaychauhan98@gmail.com>
* chore: update auto-generated files after package.json changes
- Update OpenAPI documentation for v2 verification endpoints
- Update yarn.lock after changing platform-libraries dependency
Co-Authored-By: somay@cal.com <somaychauhan98@gmail.com>
* refactor: extract verification logic from tRPC handlers into exportable functions
- Refactor sendVerifyEmailCode.handler.ts to extract core logic into sendVerifyEmailCode function
- Refactor verifyCodeUnAuthenticated.handler.ts to extract core logic into verifyCodeUnAuthenticated function
- Refactor organizations/verifyCode.handler.ts to extract core logic into verifyCodeAuthenticated function
- Update platform/libraries/index.ts to import from refactored handler files instead of standalone verification.ts
- Remove standalone verification.ts file as requested by user
- Keep original tRPC handlers as wrappers that call the extracted functions
- Maintain backward compatibility for existing tRPC endpoints
Co-Authored-By: somay@cal.com <somaychauhan98@gmail.com>
* extract logic into seperate functions
* Update index.ts
* refactor: remove unused type imports from verification-atom service
* feat: create v2 atoms input/output types for verification endpoints
- Add SendVerificationEmailInput and VerifyEmailCodeInput with validation decorators
- Add SendVerificationEmailOutput and VerifyEmailCodeOutput following v2 atoms patterns
- Update atoms verification controller to use custom types instead of platform types
- Auto-update openapi.json with new type definitions
Co-Authored-By: somay@cal.com <somaychauhan98@gmail.com>
* fix: add missing type imports to verification service
- Import ZVerifyCodeInputSchema from @calcom/prisma/zod-utils
- Import VerifyCodeAuthenticatedInput from organizations handler
- Import TSendVerifyEmailCodeSchema from sendVerifyEmailCode schema
- Resolves CI build failure in API v2 tests
Co-Authored-By: somay@cal.com <somaychauhan98@gmail.com>
* feat: add email verification check endpoint and refactor verification flow
* added Throttle
* added chagelog
* chore: update platform libraries to 0.0.317
* refactor: remove unused context and update email verification query key dependencies
* chore: bump @calcom/platform-libraries from 0.0.318 to 0.0.319
* Update verifyCode.handler.ts
* chore: bump @calcom/platform-libraries from 0.0.319 to 0.0.320
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* fix manage test error
* fix manage test error
* update useBookerContext
* wrap store provider around booker
* replace useStore with useBookerStoreContext
* replace useBookerStore with useBookerStoreContext
* add initializer function for booker store provider
* update props
* fixup: pass more props
* export StoreInitializeType type
* replace useBookerStore with useBookerStoreContext
* fixup: dont wrap BookerStoreProvider around booker directly
* wrap BookerStoreProvider around booker web wrapper and fix local storage import
* fix: wrap test components with BookerStoreProvider to fix failing unit tests
- Create reusable test utility in test-utils.tsx with comprehensive mock store
- Update Booker.test.tsx to use context-based testing approach
- Fix DatePicker tests in both bookings and calendars packages
- Simulate auto-advance behavior for month navigation tests
- All 14 previously failing tests now pass
Co-Authored-By: rajiv@cal.com <sahalrajiv6900@gmail.com>
* add changesets
* fix: complete migration from useBookerStore to useBookerStoreContext
- Updated all remaining files to use useBookerStoreContext instead of useBookerStore
- Fixed BookingFields.test.tsx by wrapping test component with BookerStoreProvider
- Ensures all Booker components work within the new context-based store pattern
- Resolves failing unit tests in CI by completing the store migration
Co-Authored-By: rajiv@cal.com <sahalrajiv6900@gmail.com>
* fix: add missing useBookerStoreContext import in BookerWebWrapper.tsx
- Fixes TypeScript errors in CI where useBookerStoreContext was used but not imported
- Completes the migration from useBookerStore to useBookerStoreContext pattern
- All tests pass locally after this fix
Co-Authored-By: rajiv@cal.com <sahalrajiv6900@gmail.com>
* Revert "fix: add missing useBookerStoreContext import in BookerWebWrapper.tsx"
This reverts commit 12947ca63f46c42e5aee74c78176ef230e2bf2cf.
* Revert "fix: complete migration from useBookerStore to useBookerStoreContext"
This reverts commit 87d837f2d30e4f9259d2be786049d21856f4eef0.
* fixup: useBookerStoreContext and useInitializeBookerStoreContext for booker web wrapper
* fixup: failing E2E tests
* fixup: email embed breaking
* fixup: troubleshooter crashing
* replace useBookerstore with useBookerStoreContext
---------
Co-authored-by: Rajiv Sahal <sahalrajiv-extc@atharvacoe.ac.in>
Co-authored-by: Ryukemeister <sahalrajiv6900@gmail.com>
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: Benny Joo <sldisek783@gmail.com>
* feat: add toggle for no availability dialog
* Create great-hands-lick.md
* fix: correct spelling from showNoAvailabilityDailog to showNoAvailabilityDialog
* remove comment and redundant
* only make api call once access token is verified
* add date fns tz
* use date-fns to format ranges for platform
* update yarn.lock
* fix merge conflicts
* fix updating overrides for atoms
* add changesets
* fix: ensure isBookingDryRun prop works for booking creation
- Add isBookingDryRun prop to useHandleBookEvent hook
- Pass prop through BookerPlatformWrapper and useBookings
- Override _isDryRun flag when prop is provided
- Fixes issue where dry run banner showed but booking creation ignored prop
Co-Authored-By: rajiv@cal.com <rajiv@cal.com>
* fixup
* if dry run prop is pass we use that, otherwise we use params
* add changesets for PR
* replace minor with patch changeset
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: rajiv@cal.com <rajiv@cal.com>
Co-authored-by: Ryukemeister <sahalrajiv6900@gmail.com>
Co-authored-by: Rajiv Sahal <sahalrajiv-extc@atharvacoe.ac.in>
Co-authored-by: Morgan <33722304+ThyMinimalDev@users.noreply.github.com>
* feat: expose AvailabilitySettingsProps type in @calcom/atoms
- Export AvailabilitySettingsPlatformWrapperProps as AvailabilitySettingsProps
- Add type export to main atoms package index for direct import
- Enables external consumers to import type directly from @calcom/atoms
Co-Authored-By: rajiv@cal.com <rajiv@cal.com>
* feat: also export AtomScheduleType for atomSchedule data
- Export FindDetailedScheduleByIdReturnType as AtomScheduleType
- Enables direct import of atomSchedule type from @calcom/atoms
- Covers both AvailabilitySettingsProps and AtomScheduleType exports
Co-Authored-By: rajiv@cal.com <rajiv@cal.com>
* fix: update AtomScheduleType to include null and undefined
Co-Authored-By: rajiv@cal.com <rajiv@cal.com>
* refactor: move AtomScheduleType to AvailabilitySettingsPlatformWrapper for cleaner organization
Co-Authored-By: rajiv@cal.com <rajiv@cal.com>
* feat: rename AtomScheduleType to AvailabilitySettingsAtomScheduleType for better clarity
Co-Authored-By: rajiv@cal.com <rajiv@cal.com>
* feat: rename to AvailabilitySettingsScheduleType for better naming consistency
Co-Authored-By: rajiv@cal.com <rajiv@cal.com>
* fix: use proper import from @calcom/platform-libraries/schedules instead of dynamic import
Co-Authored-By: rajiv@cal.com <rajiv@cal.com>
* add changelogs
* feat: extract AvailabilitySettingsSchedule type from AvailabilitySettingsProps
- Extract schedule property structure into separate AvailabilitySettingsSchedule type
- Update AvailabilitySettingsProps to reuse the extracted schedule type
- Export AvailabilitySettingsSchedule from @calcom/atoms package index
- Enables direct import of schedule type for external consumers
Co-Authored-By: rajiv@cal.com <rajiv@cal.com>
* Revert "feat: extract AvailabilitySettingsSchedule type from AvailabilitySettingsProps"
This reverts commit 79239e4b18925db3fcc1d8df7e9f37770ec4f116.
* fixup: extract schedule for AvailabilitySettingsProps
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: rajiv@cal.com <rajiv@cal.com>
Co-authored-by: Rajiv Sahal <sahalrajiv-extc@atharvacoe.ac.in>
Co-authored-by: Ryukemeister <sahalrajiv6900@gmail.com>
* Add dep versions
* Release new version for embeds
* Add prepublish
* Use prepare script which works with both npm and yarn
* Add changesets correctly
* Add embed publishing command
---------
Co-authored-by: zomars <zomars@me.com>
