Cal.com - update eventType to eventTypeId

[michelle0927]

Resolves #16323

Summary by CodeRabbit

• New Features
  • Improved property names and descriptions for booking and event type fields to enhance clarity in actions and app configuration.
  • Updated descriptions for start and end time fields to include ISO 8601 format examples.
  • Enhanced error handling with detailed messages for booking creation issues.
• Bug Fixes
  • None.
• Chores
  • Updated component and package versions.
  • Updated dependency versions for compatibility.
  • Minor wording changes in action descriptions for consistency.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		Apr 22, 2025 7:53pm
pipedream-docs	⬜️ Ignored (Inspect)			Apr 22, 2025 7:53pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Apr 22, 2025 7:53pm

[coderabbitai]

Walkthrough

This update focuses on renaming and clarifying property names and descriptions across Cal.com integration components. The primary change is the renaming of eventType to eventTypeId in both the app definition and the create-booking action, aligning with the Cal.com API requirements. Similarly, booking is renamed to bookingId in relevant properties and actions. Descriptions have been updated for clarity, and ISO 8601 examples were added for date fields. Several version numbers were incremented, and a dependency update was made in the package metadata. No control flow or logic changes were introduced.

Changes

Files / Grouped Files	Change Summary
components/cal_com/actions/create-booking/create-booking.mjs	Renamed eventType to eventTypeId throughout; updated descriptions; added ISO 8601 examples; incremented version.
components/cal_com/actions/delete-booking/delete-booking.mjs components/cal_com/actions/get-booking/get-booking.mjs	Renamed booking to bookingId throughout; updated descriptions; incremented version.
components/cal_com/cal_com.app.mjs	Renamed booking to bookingId and eventType to eventTypeId in prop definitions; updated labels and descriptions.
components/cal_com/sources/booking-cancelled/booking-cancelled.mjs components/cal_com/sources/booking-created/booking-created.mjs components/cal_com/sources/booking-rescheduled/booking-rescheduled.mjs components/cal_com/sources/booking-ended/booking-ended.mjs	Incremented version numbers only.
components/cal_com/package.json	Updated package version to 0.0.5; updated @pipedream/platform dependency version.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CreateBookingAction
    participant CalComAPI

    User->>CreateBookingAction: Provide eventTypeId, startTime, endTime, etc.
    CreateBookingAction->>CalComAPI: POST /bookings with eventTypeId and booking details
    CalComAPI-->>CreateBookingAction: Booking created response
    CreateBookingAction-->>User: Return booking confirmation

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Use eventTypeId instead of eventType parameter in create-booking action (#16323)	✅

Poem

A hop and a skip, a field of green,
Properties renamed, code now pristine!
eventTypeId hops in, bookingId too,
Clearer descriptions, all shiny and new.
With version bumps and docs in tow,
This bunny’s code is ready to go! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/cal_com/actions/create-booking/create-booking.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2f4496c and ca39775.

📒 Files selected for processing (1)

• components/cal_com/actions/create-booking/create-booking.mjs (4 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• components/cal_com/actions/create-booking/create-booking.mjs

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Publish TypeScript components
• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base
• GitHub Check: Verify TypeScript components

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[jcortes]

Hi @michelle0927 lgtm! Ready for QA!

[michelle0927]

/approve