[Google Drive] fix create folder action

[andrewjschuang]

WHY

When creating a folder with a unique name, we encountered a special case where the parent folder was located in a shared folder within a shared drive that the user did not have direct access to. As a result, the parent folder could not be found using the search query.

Changing the corpora parameter to user resolved the issue.

Summary by CodeRabbit

• New Features
  • Enhanced folder creation logic in Google Drive for improved query capabilities, including support for shared folders.
• Version Updates
  • Updated component version from 0.1.7 to 0.1.8.
  • Updated package version from 0.8.5 to 0.8.6.

[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)			Oct 10, 2024 2:29pm
pipedream-docs	⬜️ Ignored (Inspect)			Oct 10, 2024 2:29pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Oct 10, 2024 2:29pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request includes updates to the create-folder.mjs file in the Google Drive component, where the version number has been incremented from "0.1.7" to "0.1.8". The logic for checking existing folders has been revised to use a new opts object, enhancing query capabilities. Additionally, the package.json file for the @pipedream/google_drive component has been updated to reflect a new version number, changing from "0.8.5" to "0.8.6", with no other modifications.

Changes

File Path	Change Summary
components/google_drive/actions/create-folder.mjs	Version updated from "0.1.7" to "0.1.8"; modified run method logic to use new opts object.
components/google_drive/package.json	Version updated from "0.8.5" to "0.8.6"; no other changes made.

Possibly related PRs

• [Google Drive] Upload File - fix file path bug #12241: The changes in the upload-file.mjs file involve a version update and modifications to the logic, similar to the version increment and logic changes in the create-folder.mjs file of the main PR.

Suggested reviewers

• lcaresia
• GTFalcao

Poem

In the drive where folders grow,
A new version starts to glow.
With options fresh, the queries flow,
Hopping high, we watch it show!
A leap for files, a joyful cheer,
In the code, we hold so dear! 🐇✨

---

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