Skip to content

Conversation

@steven-tey
Copy link
Collaborator

@steven-tey steven-tey commented Jun 5, 2025

Summary by CodeRabbit

  • New Features
    • Enhanced validation for incoming data, providing more detailed error messages and including additional information for already backfilled entries.
  • Improvements
    • Optimized lead event fetching by supporting multiple link IDs in a single request, improving efficiency for batch operations.

@vercel
Copy link
Contributor

vercel bot commented Jun 5, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
dub ✅ Ready (Inspect) Visit Preview Jun 5, 2025 4:17pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 5, 2025

Walkthrough

The changes introduce and update the getFramerLeadEvents Tinybird pipe query to support fetching lead event data for multiple link IDs at once. The validation and processing logic in the backfill API is enhanced to use this data, attaching additional information to invalid entries. Parameter schemas and function calls are updated accordingly.

Changes

File(s) Change Summary
apps/web/app/(ee)/api/cron/framer/backfill-leads-batch/route.ts Added getFramerLeadEvents pipe; updated POST handler to fetch lead events, enhance validation, and attach clickId to invalid entries.
apps/web/scripts/framer/backfill-remainder.ts Updated getFramerLeadEvents parameter schema to accept multiple link IDs; adjusted function calls to match.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant API (POST handler)
    participant Tinybird Pipe
    participant Redis

    Client->>API (POST handler): Send payload with entries
    API (POST handler)->>Tinybird Pipe: getFramerLeadEvents(linkIds)
    Tinybird Pipe-->>API (POST handler): Return lead events for linkIds
    loop For each payload entry
        API (POST handler)->>Redis: Check if backfilled (externalId:eventName)
        Redis-->>API (POST handler): Backfill status
        alt Link missing
            API (POST handler)-->>Client: Mark entry invalid (missing link)
        else Already backfilled
            API (POST handler)-->>Client: Mark entry invalid (already backfilled) + attach clickId
        end
    end
    API (POST handler)-->>Client: Return results
Loading

Poem

A batch of leads, a flurry of links,
The pipes now fetch more than one, methinks!
With clickIds in tow and validation anew,
The backfill is smarter, the process more true.
Hopping through data, the rabbit’s delight—
Many IDs handled, all in one byte!
🐇✨


📜 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 aa0fa0d and 7891b26.

📒 Files selected for processing (1)
  • apps/web/app/(ee)/api/cron/framer/backfill-leads-batch/route.ts (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/web/app/(ee)/api/cron/framer/backfill-leads-batch/route.ts
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build
✨ Finishing Touches
  • 📝 Generate Docstrings

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

@steven-tey steven-tey requested review from Copilot and devkiran June 5, 2025 15:50
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the backfill workflows to accept multiple link IDs and surfaces the clickId for events that have already been backfilled.

  • Switches the Framer pipeline to use a linkIds parameter (string or array) in both scripts.
  • Returns clickId for entries marked “Already backfilled.” in the batch route.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
apps/web/scripts/framer/backfill-remainder.ts Changed getFramerLeadEvents to take linkIds (string or array) and updated its invocation.
apps/web/app/(ee)/api/cron/framer/backfill-leads-batch/route.ts Duplicated pipeline definition; added clickId to invalid entries and reordered checks.
Comments suppressed due to low confidence (4)

apps/web/scripts/framer/backfill-remainder.ts:14

  • Duplicate definition of getFramerLeadEvents pipeline appears in two locations; extracting this into a shared module (e.g., lib/tinybird) would reduce code duplication and keep both callers in sync.
const getFramerLeadEvents = tb.buildPipe({

apps/web/scripts/framer/backfill-remainder.ts:19

  • Consider adding unit tests for this transform to verify correct behavior when passing a single string, a comma-separated string, and an array of strings.
.transform((v) => (Array.isArray(v) ? v : v.split(",")))

apps/web/app/(ee)/api/cron/framer/backfill-leads-batch/route.ts:102

  • [nitpick] Using Array.map purely for side effects can be misleading; switch to forEach or a for...of loop to clarify intent.
originalPayload.map((p, index) => {

apps/web/app/(ee)/api/cron/framer/backfill-leads-batch/route.ts:120

  • [nitpick] The message "Already backfilled." is rather generic; consider honing it (e.g., "Event already backfilled") and/or including the associated link ID for clearer debugging.
error: "Already backfilled.",

@steven-tey steven-tey merged commit fd11c28 into main Jun 5, 2025
5 of 7 checks passed
@steven-tey steven-tey deleted the return-clickid branch June 5, 2025 16:14
@coderabbitai coderabbitai bot mentioned this pull request Oct 2, 2025
@coderabbitai coderabbitai bot mentioned this pull request Oct 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants