Google slides update import

[michelle0927]

Updates @pipedream/google_drive import.

Summary by CodeRabbit

• Chores
  • Updated version numbers for various Google Slides actions and sources.
  • Upgraded package version and adjusted dependency order.
  • Added a new dependency for Google Drive integration.
  • Modified Google Drive integration to use an external package.

[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)			Jul 29, 2025 4:25pm
pipedream-docs	⬜️ Ignored (Inspect)			Jul 29, 2025 4:25pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Jul 29, 2025 4:25pm

[coderabbitai]

Walkthrough

This update increments version numbers for several Google Slides action and source modules, updates the package version and dependencies in package.json, and changes the import of the Google Drive module in the main app file to use an external package. No functional or logical code changes were made.

Changes

Cohort / File(s)	Change Summary
Version Bumps (Actions & Sources) components/google_slides/actions/create-presentation/create-presentation.mjs, components/google_slides/actions/find-presentation/find-presentation.mjs, components/google_slides/actions/merge-data/merge-data.mjs, components/google_slides/actions/refresh-chart/refresh-chart.mjs, components/google_slides/sources/new-presentation/new-presentation.mjs	Incremented the version property in the exported default objects for each file.
App Import Update components/google_slides/google_slides.app.mjs	Changed the Google Drive app import from a local path to the external @pipedream/google_drive package.
Package Metadata components/google_slides/package.json	Incremented package version, reordered dependencies, and added @pipedream/google_drive as a dependency.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop and a skip, some numbers anew,
The Slides and their friends got a version or two.
With Drive now imported from a package so neat,
Dependencies shuffled, the update’s complete!
No logic has changed, just a version parade—
A rabbit’s small dance for the progress we’ve made.
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 e106c71 and 7adfab4.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (7)

• components/google_slides/actions/create-presentation/create-presentation.mjs (1 hunks)
• components/google_slides/actions/find-presentation/find-presentation.mjs (1 hunks)
• components/google_slides/actions/merge-data/merge-data.mjs (1 hunks)
• components/google_slides/actions/refresh-chart/refresh-chart.mjs (1 hunks)
• components/google_slides/google_slides.app.mjs (1 hunks)
• components/google_slides/package.json (2 hunks)
• components/google_slides/sources/new-presentation/new-presentation.mjs (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

components/google_slides/package.json (1)

Learnt from: jcortes
PR: #14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like fs to package.json dependencies, as they are native modules provided by the Node.js runtime.

🔇 Additional comments (8)

components/google_slides/actions/find-presentation/find-presentation.mjs (1)

7-7: Version bump acknowledged – no issues spotted
Patch-level increment from 0.0.2 → 0.0.3 is consistent with the rest of the package updates.

components/google_slides/actions/create-presentation/create-presentation.mjs (1)

7-7: Version bump looks good
The patch upgrade aligns with the other action modules.

components/google_slides/actions/refresh-chart/refresh-chart.mjs (1)

7-7: Patch version increment confirmed
No functional changes detected beyond the version field.

components/google_slides/actions/merge-data/merge-data.mjs (1)

7-7: Minor version update OK
0.0.1 → 0.0.2 is coherent with the coordinated release bump.

components/google_slides/sources/new-presentation/new-presentation.mjs (1)

9-9: Version bump accepted
The source moves from 0.0.3 → 0.0.4. Ensure accompanying docs/changelog reflect this.

components/google_slides/package.json (2)

3-3: Semantic-version bump looks good
Incrementing the package version to 0.1.2 is consistent with the non-breaking nature of the change.

---

13-15: External dependency switch verified – no stale imports found
Ran a repository-wide search for ../google_drive/google_drive.app.mjs and found no occurrences. The migration to @pipedream/google_drive is complete.

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

2-4: Import swap to packaged app LGTM
Switching to @pipedream/google_drive keeps the component self-contained and avoids local path coupling. No further issues spotted.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch google-slides-update-import

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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 generate unit tests to generate unit tests for 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.

[jcortes]

Hi @michelle0927 lgtm! Ready for Release!