Dhairyashil ShindeandGitHub
3ee24586a7
* feat(api): PATCH Event Type V2 API to support all current locations * docs(api): update locations documentation and add E2E tests for new integrations - Updated locations property documentation in create-event-type.input.ts and update-event-type.input.ts to clarify app installation requirements - Explained that only Google Meet, MS Teams, and Zoom can be installed via API - Noted that Cal Video is installed by default - Added E2E tests for creating and updating event types with newly supported integration locations (jitsi, zoom, google-meet, whereby, huddle, element-call) - Regenerated openapi.json with updated API documentation Addresses feedback from Lauris regarding platform API location support. * fix(api): use supportedIntegrations list for app validation Updated checkAppIsValidAndConnected to use the full supportedIntegrations list from locations.input.ts instead of hardcoded array. This allows all 27 supported conferencing apps to be set as event type locations via API, as long as they are already connected by the user. * fix(api): add slug mapping for all conferencing integrations Added comprehensive slug mapping to translate API integration names (e.g., 'facetime-video', 'whereby-video') to actual app slugs (e.g., 'facetime', 'whereby'). This ensures the app lookup works correctly for all 27 supported conferencing integrations. Addresses AI bot feedback about slug mismatches. * fix(api): add missing huddle to huddle01 slug mapping Added mapping for huddle -> huddle01. Other apps like tandem, jitsi, cal-video, google-meet, and zoom don't need mapping as their API names already match their app slugs (handled by the fallback || appSlug). * update key * update ket * test(api): update E2E tests to validate newly supported integrations Replaced end-to-end tests with validation-focused tests that follow the existing pattern. The new test creates event types with various newly supported integrations (jitsi, whereby-video, huddle, tandem, element-call-video) directly in the database (bypassing app connection checks) and verifies the API correctly returns them. This approach tests that the input validation accepts all 27 supported integration types without requiring actual app installations in the test environment. * fix(api): correct slug mappings for whatsapp, shimmer, and jelly integrations - Fixed whatsapp-video mapping from 'whatsappvideo' to 'whatsapp' - Fixed shimmer-video mapping from 'shimmer' to 'shimmervideo' - Fixed jelly-conferencing mapping from 'jelly-conferencing' to 'jelly' All slug mappings now correctly match the actual app slugs in packages/app-store/*/config.json files. This ensures proper app validation when users create/update event types with these locations. Addresses feedback from @pedroccastro * updated openapi.json file because of main branch code * test(api): add negative test for unsupported integration locations - Added E2E test to validate 400 error when creating event type with unsupported integration - Test verifies exact error message listing all supported integrations - Uses imported supportedIntegrations constant for maintainability - Follows same pattern as booking fields validation tests Addresses feedback from @supalarry * test(api): add negative test for patching event type with unconnected integration - Added E2E test to validate 400 error when user tries to PATCH event type with jitsi integration they haven't connected - Test verifies exact error message 'jitsi not connected.' - Follows existing test patterns with proper cleanup
Mintlify Starter Kit
Click on Use this template to copy the Mintlify starter kit. The starter kit contains examples including
- Guide pages
- Navigation
- Customizations
- API Reference pages
- Use of popular components
Development
Install the Mintlify CLI to preview the documentation changes locally. To install, use the following command
npm i -g mintlify
Run the following command at the root of your documentation (where mint.json is)
mintlify dev
Publishing Changes
Install our Github App to auto propagate changes from your repo to your deployment. Changes will be deployed to production automatically after pushing to the default branch. Find the link to install on your dashboard.
Troubleshooting
- Mintlify dev isn't running - Run
mintlify installit'll re-install dependencies. - Page loads as a 404 - Make sure you are running in a folder with
mint.json