* feat: add API endpoint to fetch Google Calendar meeting details and metrics * refactor: rename eventId to eventUid and update calendar event details endpoint * feat: implement Google Calendar service account delegation for event details * refactor: simplify Google Calendar event response * refactor: simplify calendar event details endpoint * feat: add calendar event details endpoint with schema and controller implementation * chore: reset platform libraries package version to 0.0.0 * refactor: migrate calendar event details to unified calendars module * Update gcal.service.ts * refactor: update calendar event schema with title and locations fields replacing summary and conferenceData * feat: update calendar event source to use enum type for better validation * update api description * refactor: make Google Calendar service methods private * refactor: remove location field from unified calendar event output * fix: update Google Calendar event location type property to match unified schema * feat: add CalendarEventStatus enum and map Google Calendar statuses to standardized values * docs: add property descriptions to calendar event schema and remove organizer field * fix: change calendar event locations type from null to empty array in unified calendar API * feat: make calendar source field required * refactor: replace organizer field with hosts array in Google calendar event mapping * feat: enhance calendar event location API documentation with detailed property descriptions * feat: add calendar event details endpoint documentation * fix: typo * docs: update calendar event details API description to remove reschedule history reference * refactor: rename uri to url in calendar event location interfaces and mappings * refactor: improve calendar event response status handling and code organization * Update get-unified-calendar-event.ts * update docs * chore: update @calcom/platform-libraries to version 0.0.215
How to work with platform libraries in Dev
We version this package using NPM: https://www.npmjs.com/package/@calcom/platform-libraries?activeTab=code
Here is the workflow:
- If you change platform libraries for the first time, then run
yarn localto build them locally for the first time. This will also make v2 api point to the local libraries. - If you change them for the second time, then run
yarn build:devto re-build them. - Once you are happy with platform libraries:
- run
yarn publish-npm- it will check "@calcom/platform-libraries" version in npm and update it's package.json to the next version and then it will publish the package to npm, update the version of "@calcom/platform-libraries" in the api v2 package.json, reset "@calcom/platform-libraries" to 0.0.0 and run yarn install.
Before Merging to main
- Publish Your Version of Libraries on NPM:
- To publish, ensure you are a contributor to the platform libraries' NPM package.
- Authenticate yourself via the CLI using npm auth.
- Increment the version number accordingly.
- Run yarn publish to publish your version.
- Once it's published, change back the version in packages/platform/libraries/package.json back to 0.0.0
- Run yarn
- You should now be using the npm package instead of the locally built version
When to publish new version of platform libraries
- New exports in the index.js of platform libraries
- Code change in the functions already exported
- Prisma schema change breaking implementation of functions in the currently used releases of platform libraries