Google Business - add debug log

[andrewjschuang]

WHY

Summary by CodeRabbit

• Chores
  • Updated patch versions for Google My Business package and sources (new post created, new review created for single and multiple locations).
  • Added lightweight internal logging to assist monitoring of retrieved reviews.
  • No functional or API changes; behavior remains the same for end users.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs	Ignored			Sep 18, 2025 6:36pm
pipedream-docs-redirect-do-not-edit	Ignored			Sep 18, 2025 6:36pm

[coderabbitai]

Walkthrough

A console log was added in components/google_my_business/sources/common.ts to output the number of fetched items within getAndProcessData. No other logic or control flow was modified.

Changes

Cohort / File(s)	Change Summary
Logging components/google_my_business/sources/common.ts	Inserted runtime console.log("Number of reviews: ", items.length) after fetching items; no changes to filtering, limiting, reversing, or emitting logic.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nudge the logs with whisker’d cheer,
“How many reviews?”—now crystal clear.
A tiny print, a gentle hop,
I count the stars that never stop.
Carrots tall, the numbers bright—
Ship it swift, by moonlit night. 🌕🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description is incomplete: it contains only the template header "## WHY" with the placeholder left empty and provides no rationale, scope, or testing information for the added debug log; the <pr_objectives> also note the WHY section is empty. Because the repository requires that template sections be filled to explain intent and impact, the current description does not meet the template requirements and leaves reviewers without necessary context. This missing information makes the description insufficient for approval.	Please complete the WHY section with the rationale for adding the debug log and link any related issue or incident, add a brief summary of what changed (file path and that this is a logging-only change), describe testing/QA steps taken and whether the log is temporary, and note any potential risks or follow-up actions; update the PR description with these details before requesting review.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "Google Business - add debug log" accurately and concisely describes the main change in the diff (a debug console.log added to the Google Business source to log review count), is specific to the affected component, and is short and easy for a reviewer to scan and understand. It does not include unrelated details or noisy elements and therefore aligns with the repository's expectations for a focused PR title. Given the raw_summary shows only a logging addition, the title correctly reflects the primary intent of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ 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-business-debug-logs

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

components/google_my_business/sources/common.ts (2)

56-56: Make the log generic, debug‑level, and opt‑in

This file is shared by multiple sources; “reviews” may be misleading, and unconditional logs can add noise. Prefer debug level and gate behind an env flag.

-      console.log("Number of reviews: ", items?.length ?? 0);
+      if (process.env.PD_DEBUG === "1") {
+        console.debug("[google_my_business] items fetched:", items?.length ?? 0);
+      }

---

57-69: Optional: move checkpoint after successful emits to avoid missed events on failures

Setting lastRun before emitting risks skipping items if the run crashes mid‑emit. Safer pattern: compute max(createTime) of emitted items and persist after emits succeed.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4636f3e and e1274c5.

📒 Files selected for processing (1)

• components/google_my_business/sources/common.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: pnpm publish
• GitHub Check: Ensure component commits modify component versions
• GitHub Check: Publish TypeScript components
• GitHub Check: Verify TypeScript components
• GitHub Check: Lint Code Base

🔇 Additional comments (1)

components/google_my_business/sources/common.ts (1)

56-56: Guard against undefined to prevent runtime crash

items.length will throw if getItems() returns undefined/null (the rest of the method already defensively uses optional chaining). Make the log null‑safe or default items to [].

Apply either:

-      console.log("Number of reviews: ", items.length);
+      console.log("Number of reviews: ", items?.length ?? 0);

Or:

-      const items: EntityWithCreateTime[] = await this.getItems();
+      const items: EntityWithCreateTime[] = (await this.getItems()) ?? [];