Lusha - fix prop

[michelle0927]

Summary by CodeRabbit

• Bug Fixes
  • Corrected property name from companiesIds to companyIds in company enrichment component
• Chores
  • Updated package version from 0.1.0 to 0.1.1
  • Updated component version from 0.0.1 to 0.0.2

[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		Dec 30, 2024 5:07pm
pipedream-docs	⬜️ Ignored (Inspect)			Dec 30, 2024 5:07pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Dec 30, 2024 5:07pm

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This pull request involves minor updates to the Lusha component, specifically in the company-enrich.mjs file and the package's package.json. The changes include renaming a property from companiesIds to companyIds and incrementing version numbers for both the component and the package. These modifications appear to be a small refinement to the existing company enrichment functionality.

Changes

File	Change Summary
components/lusha/actions/company-enrich/company-enrich.mjs	- Renamed companiesIds property to companyIds - Updated version from "0.0.1" to "0.0.2"
components/lusha/package.json	- Updated package version from "0.1.0" to "0.1.1"

Possibly related PRs

• New Components - lusha #14994: Introduces a new module in company-enrich.mjs with similar property renaming

Suggested labels

bug

Poem

🐰 A Rabbit's Versioning Verse 🐰

Hop, hop, through the code we go,
Renaming props with a gentle flow,
companiesIds to companyIds so neat,
A version bump makes our changes complete!

Coding magic, small and bright! 🚀

---

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>, 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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5ce280f and 6dc1088.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• components/lusha/actions/company-enrich/company-enrich.mjs (2 hunks)
• components/lusha/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• components/lusha/package.json

🔇 Additional comments (1)

components/lusha/actions/company-enrich/company-enrich.mjs (1)

7-7: Minor version bump looks good.

Incrementing from 0.0.1 to 0.0.2 in this file is consistent with the small scope of these changes.

[GTFalcao]

LGTM!