Fix validate-connector script

[mit-27]

• Closes Fix validate-connectors script #424

[changeset-bot]

⚠️ No Changeset found

Latest commit: c206663

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@mit-27 is attempting to deploy a commit to the Panora Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The recent updates in the connectorUpdate.js script involve renaming parameters, enhancing logic for case handling, and improving the import statement generation. These changes are aimed at refining the functionality and accuracy of the script in managing connector updates and mappings in a more dynamic and robust manner.

Changes

File	Change Summary
.../connectorUpdate.js	Renamed serviceNames to possibleProviders, added capitalization and null handling logic, updated mappingEntry, and integrated new function calls for provider retrieval and import statement generation.

Assessment against linked issues

Objective	Addressed	Explanation
Fix validate-connectors script by ensuring object's input and output types are added in src/core/utils/types/original/original.vertical.ts file. (#424)	❓	The changes mention logic additions for handling Original${objectType}Input and Original${objectType}Output, but it's unclear if these are directly added to the specified file.

Poem

🐇✨
Oh, hop hop hooray, for the code that's anew,
With tweaks and twirls, it's fresh like morning dew.
From serviceNames to providers we leap,
Ensuring our connectors are never asleep.
So here's to changes, both big and small,
May our code run swift - bugs beware, y'all!
🌟🐰

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c3a2c05 and c206663.

Files selected for processing (1)

• packages/api/scripts/connectorUpdate.js (7 hunks)

Files not reviewed due to errors (1)

• packages/api/scripts/connectorUpdate.js (no review received)