Skip to content

send email provider to loops#862

Merged
elie222 merged 2 commits intomainfrom
feat/loops-provider
Oct 22, 2025
Merged

send email provider to loops#862
elie222 merged 2 commits intomainfrom
feat/loops-provider

Conversation

@elie222
Copy link
Owner

@elie222 elie222 commented Oct 21, 2025

Summary by CodeRabbit

  • Bug Fixes

    • Improved error handling and logging during user sign-up and contact creation for more reliable recoveries.
    • Enhanced retrieval of account-provider info to reduce signup failures.
  • New Features

    • Sign-up/contact creation now includes provider details to improve downstream integrations.
  • Chores

    • Version bumped to v2.17.6.

@vercel
Copy link

vercel bot commented Oct 21, 2025

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

Project Deployment Preview Updated (UTC)
inbox-zero Ready Ready Preview Oct 22, 2025 9:57am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 21, 2025

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Refactors Loops contact creation to fetch and pass account provider before creating a contact, updates packages/loops by removing abTestId logic and adding an optional provider parameter to createContact, and bumps version to v2.17.6.

Changes

Cohort / File(s) Summary
Auth flow / Loops invocation
apps/web/utils/auth.ts
Move Loops contact creation into an async function that queries the account by userId to obtain provider, log and capture account lookup errors, and invoke loops() (not a pre-created promise) inside Promise.all alongside Resend and Dub tasks.
Loops API wrapper
packages/loops/src/loops.ts
Add optional provider?: string to createContact(email, firstName?, provider?); include firstName and provider in properties passed to loops.createContact; remove getRandomInt and abTestId logic; simplify several functions to return loops.* calls directly and streamline deleteContact.
Version bump
version.txt
Update version from v2.17.5 to v2.17.6.

Sequence Diagram

sequenceDiagram
    actor User
    participant Auth as handleSignIn
    participant DB as Account DB
    participant Loops as Loops API
    participant Resend as Resend API
    participant Dub as Dub Tracking

    User->>Auth: Sign in (new user)
    Auth->>DB: Fetch account by userId
    DB-->>Auth: Account (with provider) or error
    par Parallel tasks
        rect rgb(200,220,255)
            Note over Auth,Loops: Loops contact creation (now uses provider)
            Auth->>Loops: createContact(email, firstName, provider)
            Loops-->>Auth: created / 409 / error
        end
        rect rgb(220,240,220)
            Note over Auth,Resend: Resend contact handling
            Auth->>Resend: create/update contact
            Resend-->>Auth: OK
        end
        rect rgb(240,220,220)
            Note over Auth,Dub: Dub sign-up tracking
            Auth->>Dub: track sign-up
            Dub-->>Auth: OK
        end
    end
    Auth-->>User: Sign-in complete
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hopped to fetch the provider name,
Loops now greets each contact the same.
No random tests, just tidy calls,
Parallel tasks and fewer falls.
Version bumped — a carrot for the game.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The pull request title "send email provider to loops" is clear, specific, and directly aligned with the main change in the changeset. The modifications show that the createContact method in the Loops package was updated to accept an optional provider parameter, and the authentication logic was refactored to retrieve and pass the provider information when creating Loops contacts. The title accurately captures this primary objective without being vague or generic, and a teammate reviewing the history would immediately understand the intent of the change.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/loops-provider

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 76d9f52 and 31ba849.

📒 Files selected for processing (1)
  • apps/web/utils/auth.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/web/utils/auth.ts
⏰ 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). (3)
  • GitHub Check: cubic · AI code reviewer
  • GitHub Check: Socket Security: Pull Request Alerts
  • GitHub Check: Socket Security: Project Report

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

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/loops/src/loops.ts (1)

4-14: Replace console.warn with createScopedLogger.

The console.warn usage violates the coding guidelines. Backend TypeScript files should use createScopedLogger for logging.

As per coding guidelines.

Apply this diff:

+import { createScopedLogger } from "@/utils/logger";
+
+const logger = createScopedLogger("loops");
+
 let loops: LoopsClient | undefined;
 function getLoopsClient(): LoopsClient | undefined {
   // if loops api key hasn't been set this package doesn't do anything
   if (!process.env.LOOPS_API_SECRET) {
-    console.warn("LOOPS_API_SECRET is not set");
+    logger.warn("LOOPS_API_SECRET is not set");
     return;
   }
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 644ec49 and 76d9f52.

📒 Files selected for processing (3)
  • apps/web/utils/auth.ts (2 hunks)
  • packages/loops/src/loops.ts (5 hunks)
  • version.txt (1 hunks)
🧰 Additional context used
📓 Path-based instructions (8)
apps/web/**/*.{ts,tsx}

📄 CodeRabbit inference engine (apps/web/CLAUDE.md)

apps/web/**/*.{ts,tsx}: Use TypeScript with strict null checks
Path aliases: Use @/ for imports from project root
Use proper error handling with try/catch blocks
Format code with Prettier
Leverage TypeScript inference for better DX

Files:

  • apps/web/utils/auth.ts
!{.cursor/rules/*.mdc}

📄 CodeRabbit inference engine (.cursor/rules/cursor-rules.mdc)

Never place rule files in the project root, in subdirectories outside .cursor/rules, or in any other location

Files:

  • apps/web/utils/auth.ts
  • packages/loops/src/loops.ts
  • version.txt
**/*.ts

📄 CodeRabbit inference engine (.cursor/rules/form-handling.mdc)

**/*.ts: The same validation should be done in the server action too
Define validation schemas using Zod

Files:

  • apps/web/utils/auth.ts
  • packages/loops/src/loops.ts
**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/logging.mdc)

**/*.{ts,tsx}: Use createScopedLogger for logging in backend TypeScript files
Typically add the logger initialization at the top of the file when using createScopedLogger
Only use .with() on a logger instance within a specific function, not for a global logger

Import Prisma in the project using import prisma from "@/utils/prisma";

**/*.{ts,tsx}: Don't use TypeScript enums.
Don't use TypeScript const enum.
Don't use the TypeScript directive @ts-ignore.
Don't use primitive type aliases or misleading types.
Don't use empty type parameters in type aliases and interfaces.
Don't use any or unknown as type constraints.
Don't use implicit any type on variable declarations.
Don't let variables evolve into any type through reassignments.
Don't use non-null assertions with the ! postfix operator.
Don't misuse the non-null assertion operator (!) in TypeScript files.
Don't use user-defined types.
Use as const instead of literal types and type annotations.
Use export type for types.
Use import type for types.
Don't declare empty interfaces.
Don't merge interfaces and classes unsafely.
Don't use overload signatures that aren't next to each other.
Use the namespace keyword instead of the module keyword to declare TypeScript namespaces.
Don't use TypeScript namespaces.
Don't export imported variables.
Don't add type annotations to variables, parameters, and class properties that are initialized with literal expressions.
Don't use parameter properties in class constructors.
Use either T[] or Array consistently.
Initialize each enum member value explicitly.
Make sure all enum members are literal values.

Files:

  • apps/web/utils/auth.ts
  • packages/loops/src/loops.ts
apps/web/utils/**

📄 CodeRabbit inference engine (.cursor/rules/project-structure.mdc)

Create utility functions in utils/ folder for reusable logic

Files:

  • apps/web/utils/auth.ts
apps/web/utils/**/*.ts

📄 CodeRabbit inference engine (.cursor/rules/project-structure.mdc)

apps/web/utils/**/*.ts: Use lodash utilities for common operations (arrays, objects, strings)
Import specific lodash functions to minimize bundle size

Files:

  • apps/web/utils/auth.ts
**/*.{js,jsx,ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)

**/*.{js,jsx,ts,tsx}: Don't use elements in Next.js projects.
Don't use elements in Next.js projects.
Don't use namespace imports.
Don't access namespace imports dynamically.
Don't use global eval().
Don't use console.
Don't use debugger.
Don't use var.
Don't use with statements in non-strict contexts.
Don't use the arguments object.
Don't use consecutive spaces in regular expression literals.
Don't use the comma operator.
Don't use unnecessary boolean casts.
Don't use unnecessary callbacks with flatMap.
Use for...of statements instead of Array.forEach.
Don't create classes that only have static members (like a static namespace).
Don't use this and super in static contexts.
Don't use unnecessary catch clauses.
Don't use unnecessary constructors.
Don't use unnecessary continue statements.
Don't export empty modules that don't change anything.
Don't use unnecessary escape sequences in regular expression literals.
Don't use unnecessary labels.
Don't use unnecessary nested block statements.
Don't rename imports, exports, and destructured assignments to the same name.
Don't use unnecessary string or template literal concatenation.
Don't use String.raw in template literals when there are no escape sequences.
Don't use useless case statements in switch statements.
Don't use ternary operators when simpler alternatives exist.
Don't use useless this aliasing.
Don't initialize variables to undefined.
Don't use the void operators (they're not familiar).
Use arrow functions instead of function expressions.
Use Date.now() to get milliseconds since the Unix Epoch.
Use .flatMap() instead of map().flat() when possible.
Use literal property access instead of computed property access.
Don't use parseInt() or Number.parseInt() when binary, octal, or hexadecimal literals work.
Use concise optional chaining instead of chained logical expressions.
Use regular expression literals instead of the RegExp constructor when possible.
Don't use number literal object member names th...

Files:

  • apps/web/utils/auth.ts
  • packages/loops/src/loops.ts
!pages/_document.{js,jsx,ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)

!pages/_document.{js,jsx,ts,tsx}: Don't import next/document outside of pages/_document.jsx in Next.js projects.
Don't import next/document outside of pages/_document.jsx in Next.js projects.

Files:

  • apps/web/utils/auth.ts
  • packages/loops/src/loops.ts
  • version.txt
🧬 Code graph analysis (1)
apps/web/utils/auth.ts (2)
apps/web/app/api/outlook/webhook/logger.ts (1)
  • logger (3-3)
apps/web/utils/error.ts (1)
  • captureException (63-75)
⏰ 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). (3)
  • GitHub Check: cubic · AI code reviewer
  • GitHub Check: test
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (4)
version.txt (1)

1-1: Version bump looks good.

The patch version increment from v2.17.5 to v2.17.6 follows semantic versioning format. However, based on the PR summary describing meaningful Loops refactoring and the addition of provider-aware functionality, consider verifying whether this warrants a minor version bump (v2.18.0) depending on your project's versioning strategy.

packages/loops/src/loops.ts (2)

16-31: LGTM! Clean implementation of provider parameter.

The addition of the optional provider parameter and dynamic properties object construction is well-implemented. The conditional property assignment ensures only provided values are included in the API call.


33-106: LGTM! Simplified return statements improve readability.

The refactor to directly return promises eliminates unnecessary intermediate variables, making the code more concise while maintaining the same functionality.

apps/web/utils/auth.ts (1)

196-196: LGTM! Proper integration with provider-aware Loops contact creation.

The Promise.all correctly invokes loops() to execute the async function, maintaining parallel execution with Resend and Dub tracking. This properly integrates with the updated createLoopsContact signature that now accepts the provider parameter.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

1 issue found across 3 files

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name="apps/web/utils/auth.ts">

<violation number="1" location="apps/web/utils/auth.ts:160">
`captureException` expects a user email as its third argument; passing `user.id` will tag Sentry errors with the wrong user email, hurting observability.</violation>
</file>

React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.

@elie222 elie222 merged commit a2292a5 into main Oct 22, 2025
12 of 13 checks passed
@elie222 elie222 deleted the feat/loops-provider branch October 22, 2025 09:57
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

No issues found across 1 file

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.

1 participant