move integration from /apps path to backend/apps path

[jiwei-aipolabs]

🏷️ Ticket

https://www.notion.so/review-merge-integration-code-1-May-1e68378d6a4780338e2ff268f18ac266?pvs=4

📝 Description

move all integration file from apps to backend/apps path

🎥 Demo (if applicable)

📸 Screenshots (if applicable)

✅ Checklist

• I have signed the Contributor License Agreement (CLA) and read the contributing guide (required)
• I have linked this PR to an issue or a ticket (required)
• I have updated the documentation related to my change if needed
• I have updated the tests accordingly (required for a bug fix or a new feature)
• All checks on CI passed

Summary by CodeRabbit

• Chores
  • Updated the API endpoint definition for GET /v1/schedules with an empty parameters schema. No functional changes to the endpoint.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
aci-dev-portal	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 1, 2025 4:21pm

[coderabbitai]

Walkthrough

A new "parameters" schema object has been introduced to the GET /v1/schedules endpoint within the functions.json file. This schema is defined as an empty object with no properties, no required fields, and does not allow additional properties. No other changes were made to the endpoint or its metadata.

Changes

File	Change Summary
backend/apps/cal_com/functions.json	Added an empty "parameters" schema object to the GET /v1/schedules endpoint definition.

Poem

In the land of code, a schema appears,
Empty and clean, it calms all our fears.
No fields to fill, no keys to find,
Just a blank slate, simple and kind.
A hop and a skip, the endpoint is neat—
This rabbit approves of changes so sweet! 🐇

---

📜 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 2cd6ced and df0af8d.

📒 Files selected for processing (1)

• backend/apps/cal_com/functions.json (1 hunks)

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

• GitHub Check: Format & Lint
• GitHub Check: Compose Tests
• GitHub Check: Format, Lint, and Test

🔇 Additional comments (1)

backend/apps/cal_com/functions.json (1)

16-22: Empty parameters schema added correctly for GET_SCHEDULES
Great addition of an explicit empty parameters object to align this endpoint with the ChatGPT function-spec and maintain parity with the other routes.

---

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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.