Skip to content

Conversation

@luancazarine
Copy link
Collaborator

@luancazarine luancazarine commented Apr 7, 2025

Resolves #12462

Summary by CodeRabbit

  • New Features

    • Introduced a function to retrieve and list appointment data.
    • Rolled out new event modules for handling appointment updates, booking creations, and contact creations.
    • Added a method to dynamically retrieve the default sorting order for resources.
  • Chores

    • Updated version numbers across components for consistency.
    • Refined event descriptions for clarity.

@luancazarine luancazarine linked an issue Apr 7, 2025 that may be closed by this pull request
@vercel
Copy link

vercel bot commented Apr 7, 2025

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 7, 2025 2:40pm
pipedream-docs ⬜️ Ignored (Inspect) Apr 7, 2025 2:40pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Apr 7, 2025 2:40pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 7, 2025

Walkthrough

This PR updates several Cliniko components. It bumps version numbers in both the patient action module and package metadata. A new method listAppointments is added to facilitate appointment retrieval via the Cliniko API. In addition, the polling logic now encapsulates sorting through a new getSort() method. New modules for handling updated appointments, booking creation, and contact creation events are introduced with updated metadata and descriptions.

Changes

File(s) Change Summary
components/cliniko/actions/get-patient/get-patient.mjs, components/cliniko/package.json Incremented version numbers ("0.1.0" → "0.1.1" in get-patient; "0.1.0" → "0.2.0" in package.json)
components/cliniko/cliniko.app.mjs Added new method listAppointments(args = {}) that calls makeRequest with the "/appointments" path
components/cliniko/sources/common/polling.mjs Introduced a new method getSort() and updated getResourcesFnArgs() to use it
components/cliniko/sources/new-appointment-updated/*.mjs New module for handling updated appointment events with metadata definitions, methods (getResourceName(), getResourcesFn(), generateMeta(), getSort()), and a test event
components/cliniko/sources/new-booking-created/new-booking-created.mjs, components/cliniko/sources/new-contact-created/new-contact-created.mjs Updated description fields (removed documentation references) and incremented version fields ("0.0.1" → "0.0.2")

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant ClinikoApp
    participant API
    Client->>ClinikoApp: Call listAppointments(args)
    ClinikoApp->>ClinikoApp: Prepare request with path "/appointments"
    ClinikoApp->>API: makeRequest({ path: "/appointments", ...args })
    API-->>ClinikoApp: Return appointment data
    ClinikoApp-->>Client: Send returned data
Loading
sequenceDiagram
    participant Polling
    participant NewAppointmentModule
    participant ClinikoAPI
    participant EventEmitter
    Polling->>NewAppointmentModule: Invoke getResourcesFn() (list appointments)
    NewAppointmentModule->>ClinikoAPI: Request updated appointments
    ClinikoAPI-->>NewAppointmentModule: Return appointment data
    NewAppointmentModule->>NewAppointmentModule: Process data via generateMeta()
    NewAppointmentModule->>EventEmitter: Emit test event with sampleEmit()
Loading

Assessment against linked issues

Objective Addressed Explanation
Implement Cliniko appointment updated webhook functionality (#12462)

Suggested reviewers

  • lcaresia

Poem

I'm a rabbit, hopping through lines of code,
Skipping through versions on a well-trodden road.
New methods and modules now join the parade,
With appointments and contacts cheerfully arrayed.
My whiskers twitch at each change so bright,
Coding in rhythm, from morning to night.
🐇🎉

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/cliniko/sources/new-appointment-updated/new-appointment-updated.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 3f02ff9 and c45b611.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • components/cliniko/sources/new-appointment-updated/new-appointment-updated.mjs (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • components/cliniko/sources/new-appointment-updated/new-appointment-updated.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

🪧 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 plan to trigger planning for file edits and PR creation.
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
components/cliniko/actions/get-patient/get-patient.mjs (1)

44-44: Fix typo in success message.

There's a typo in the success message: "Suceesfully" should be "Successfully".

- $.export("$summary", `Suceesfully retrieved patient with ID: \`${response.id}\``);
+ $.export("$summary", `Successfully retrieved patient with ID: \`${response.id}\``);
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7733832 and 3f02ff9.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (8)
  • components/cliniko/actions/get-patient/get-patient.mjs (1 hunks)
  • components/cliniko/cliniko.app.mjs (1 hunks)
  • components/cliniko/package.json (1 hunks)
  • components/cliniko/sources/common/polling.mjs (1 hunks)
  • components/cliniko/sources/new-appointment-updated/new-appointment-updated.mjs (1 hunks)
  • components/cliniko/sources/new-appointment-updated/test-event.mjs (1 hunks)
  • components/cliniko/sources/new-booking-created/new-booking-created.mjs (1 hunks)
  • components/cliniko/sources/new-contact-created/new-contact-created.mjs (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: pnpm publish
🔇 Additional comments (13)
components/cliniko/package.json (1)

3-3: Version bump from 0.1.0 to 0.2.0 looks appropriate.

The minor version increment follows semantic versioning principles and appears suitable for the addition of new functionality (new appointment-related features) that would be introduced in this PR.

components/cliniko/actions/get-patient/get-patient.mjs (1)

7-7: Version bump from 0.1.0 to 0.1.1 is appropriate.

The patch version increment follows semantic versioning principles and is suitable since no functionality changes were made to this component.

components/cliniko/cliniko.app.mjs (1)

105-110: New listAppointments method follows consistent pattern.

The implementation matches the pattern of other listing methods in the file (listPatients, listContacts, listBookings) which is good for code consistency.

components/cliniko/sources/common/polling.mjs (2)

31-33: New getSort method provides good extensibility.

Adding this method allows child classes to override the default sort behavior, which is good for extensibility. This is likely used by the appointment updated webhook functionality referenced in the PR title.


39-39: Using the getSort method instead of hardcoded sorting.

Great refactoring to use the new getSort() method instead of hardcoding the sort parameter. This makes the code more maintainable and allows for customization in derived classes.

components/cliniko/sources/new-booking-created/new-booking-created.mjs (2)

8-8: Description updated for clarity.

The documentation link has been removed from the description, simplifying it to a clear statement of functionality.


10-10: Version bump to 0.0.2.

The version increment follows semantic versioning principles, indicating minor updates without breaking changes.

components/cliniko/sources/new-contact-created/new-contact-created.mjs (2)

8-8: Description updated for clarity.

The documentation link has been removed from the description, simplifying it to a clear statement of functionality.


10-10: Version bump to 0.0.2.

The version increment follows semantic versioning principles, indicating minor updates without breaking changes.

components/cliniko/sources/new-appointment-updated/test-event.mjs (1)

1-78: Well-structured test event sample.

This new test event file provides a comprehensive sample of an appointment object from the Cliniko API, including all necessary fields and relationships. The structure is consistent with other test events in the codebase.

components/cliniko/sources/new-appointment-updated/new-appointment-updated.mjs (3)

1-33: Well-implemented appointment update trigger.

The source is well-structured following the established patterns in the codebase. Good implementation details:

  1. The generateMeta method includes both the appointment ID and update timestamp in the deduplication ID, correctly handling multiple updates to the same appointment
  2. The getSort() method sorts by updated_at:desc, ensuring the most recent updates are processed first
  3. Version starts at 0.0.2 to maintain consistency with other updated components

20-26: Unique ID generation for appointment updates.

The combination of resource.id and resource.updated_at in the ID field creates a unique identifier for each update to an appointment, allowing the system to detect and process multiple updates to the same appointment as separate events.


27-29: Efficient sorting strategy.

Sorting by updated_at:desc ensures that the most recently updated appointments are processed first, which is optimal for a trigger that monitors updates.

Copy link
Collaborator

@michelle0927 michelle0927 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@vunguyenhung vunguyenhung merged commit 7db2dc4 into master Apr 8, 2025
11 checks passed
@vunguyenhung vunguyenhung deleted the 12462-trigger-cliniko---new-appointment-updated-webhook branch April 8, 2025 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[TRIGGER] Cliniko - New Appointment updated Webhook

4 participants