Conversation
|
Warning Rate limit exceeded@elie222 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 14 minutes and 23 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
WalkthroughAdds post-request UTM persistence via Next.js after hooks to onboarding and welcome pages using a new helper fetchUserAndStoreUtms. Removes the previous after hook from welcome-redirect. Introduces a scoped logger and new helper in utms.tsx, and augments storeUtms with info logs and error handling. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant Client
participant Page as Page (onboarding/welcome)
participant After as after() hook
participant Auth as auth()
participant UTM as fetchUserAndStoreUtms()
participant DB as Database
Client->>Page: Request page
Page-->>Client: Render response
Note over Page,After: Post-request phase
rect rgba(200,235,255,0.25)
Page->>After: Register after(async ...)
After->>Auth: await auth()
Auth-->>After: { user? }
alt user present
After->>UTM: fetchUserAndStoreUtms(user.id)
UTM->>DB: Select user (utms)
alt utms missing
UTM->>DB: storeUtms(user.id)
DB-->>UTM: persisted
else utms present
UTM-->>After: no-op
end
else no user
After-->>Page: no-op
end
end
Note over Client,Page: welcome-redirect no longer triggers after() UTM store
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
✨ Finishing Touches
🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
Status, Documentation and Community
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Claude finished @elie222's task —— View job PR Review: Fix UTMsI've reviewed the UTM handling implementation across all 4 modified files. Here's my comprehensive feedback: Tasks
📋 SummaryThis PR implements UTM parameter tracking by storing UTM data from cookies into the user database. The changes add UTM collection calls to the onboarding and welcome pages, create a dedicated UTM handling module, and remove UTM-related code from the welcome-redirect page. 🎯 Code Quality & Best Practices✅ Good Practices:
🐛 Potential Bugs & Issues🔴 Critical Issues:
🟡 Minor Issues:
🔒 Security Concerns
Recommendations: // Add validation in utms.tsx
const validateUtmValue = (value: string | undefined): string | undefined => {
if (!value || value.length > 255) return undefined;
// Remove potentially dangerous characters
return value.replace(/[<>\"']/g, '');
};⚡ Performance Considerations✅ Good Performance:
🔄 Potential Optimizations:
🧪 Test Coverage❌ Missing Tests:
Recommended Tests: // Example test cases needed:
describe('UTM Storage', () => {
it('should store valid UTM parameters')
it('should handle missing UTM cookies gracefully')
it('should not overwrite existing UTM data')
it('should sanitize malicious UTM values')
it('should handle database errors gracefully')
})📁 File-Specific Feedback
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
apps/web/app/(landing)/welcome/utms.tsx (2)
30-36: Bug: Writing undefined into a Prisma JSON column.Prisma JSON does not accept undefined. Coalesce to null (or omit keys) before update.
- const utms = { - utmCampaign: utmCampaign?.value, - utmMedium: utmMedium?.value, - utmSource: utmSource?.value, - utmTerm: utmTerm?.value, - affiliate: affiliate?.value, - }; + const utms = { + utmCampaign: utmCampaign?.value ?? null, + utmMedium: utmMedium?.value ?? null, + utmSource: utmSource?.value ?? null, + utmTerm: utmTerm?.value ?? null, + affiliate: affiliate?.value ?? null, + } as const; + + // Skip if no UTM cookies were present + const hasAnyUtm = Object.values(utms).some( + (v) => typeof v === "string" && v.length > 0, + ); + if (!hasAnyUtm) { + logger.info("No UTM cookies present; skipping store", { userId }); + return; + }
38-41: Make storage idempotent under concurrent after hooks.Use updateMany with a guard so we only write when utms is still null, avoiding races from multiple pages.
- await prisma.user.update({ - where: { id: userId }, - data: { utms }, - }); + await prisma.user.updateMany({ + where: { id: userId, utms: null }, + data: { utms }, + });
♻️ Duplicate comments (1)
apps/web/app/(app)/[emailAccountId]/onboarding/page.tsx (1)
24-28: Same after-hook hardening as welcome page.Centralize error handling inside fetchUserAndStoreUtms to avoid unhandled rejections.
🧹 Nitpick comments (4)
apps/web/app/(landing)/welcome/page.tsx (2)
22-24: Always pass a radix to parseInt.Prevents accidental non‑decimal parsing and aligns with code in onboarding page.
- const questionIndex = searchParams.question - ? Number.parseInt(searchParams.question) - : 0; + const questionIndex = searchParams.question + ? Number.parseInt(searchParams.question, 10) + : 0;
17-19: searchParams type: force should be string, not boolean.Next App Router passes query params as strings. Align with onboarding page typing.
export default async function WelcomePage(props: { - searchParams: Promise<{ question?: string; force?: boolean }>; + searchParams: Promise<{ question?: string; force?: string }>; }) {apps/web/app/(landing)/welcome/utms.tsx (2)
21-22: Use a function-scoped logger with context.Attaches userId once and avoids repeating it.
export async function storeUtms(userId: string) { - logger.info("Storing utms", { userId }); + const log = logger.with({ userId }); + log.info("Storing utms"); … - logger.info("Stored utms", { utms, userId }); + log.info("Stored utms", { utms }); }Also applies to: 43-44
3-6: Minor: this module contains no JSX — consider .ts extension.Renaming to utms.ts reduces noise in tooling and aligns with conventions.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (4)
apps/web/app/(app)/[emailAccountId]/onboarding/page.tsx(2 hunks)apps/web/app/(landing)/welcome-redirect/page.tsx(0 hunks)apps/web/app/(landing)/welcome/page.tsx(2 hunks)apps/web/app/(landing)/welcome/utms.tsx(2 hunks)
💤 Files with no reviewable changes (1)
- apps/web/app/(landing)/welcome-redirect/page.tsx
🧰 Additional context used
📓 Path-based instructions (14)
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/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx
apps/web/app/**
📄 CodeRabbit inference engine (apps/web/CLAUDE.md)
NextJS app router structure with (app) directory
Files:
apps/web/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx
apps/web/**/*.tsx
📄 CodeRabbit inference engine (apps/web/CLAUDE.md)
apps/web/**/*.tsx: Follow tailwindcss patterns with prettier-plugin-tailwindcss
Prefer functional components with hooks
Use shadcn/ui components when available
Ensure responsive design with mobile-first approach
Follow consistent naming conventions (PascalCase for components)
Use LoadingContent component for async data
Useresult?.serverErrorwithtoastErrorandtoastSuccess
UseLoadingContentcomponent to handle loading and error states consistently
Passloading,error, and children props toLoadingContent
Files:
apps/web/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx
!{.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/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx
**/*.tsx
📄 CodeRabbit inference engine (.cursor/rules/form-handling.mdc)
**/*.tsx: Use React Hook Form with Zod for validation
Validate form inputs before submission
Show validation errors inline next to form fields
Files:
apps/web/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx
**/*.{ts,tsx}
📄 CodeRabbit inference engine (.cursor/rules/logging.mdc)
**/*.{ts,tsx}: UsecreateScopedLoggerfor logging in backend TypeScript files
Typically add the logger initialization at the top of the file when usingcreateScopedLogger
Only use.with()on a logger instance within a specific function, not for a global loggerImport 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/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx
apps/web/app/**/*.tsx
📄 CodeRabbit inference engine (.cursor/rules/project-structure.mdc)
Components with
onClickmust be client components withuse clientdirective
Files:
apps/web/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx
**/*.{js,jsx,ts,tsx}
📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)
**/*.{js,jsx,ts,tsx}: Don't useelements 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/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx
!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/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx
**/*.{jsx,tsx}
📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)
**/*.{jsx,tsx}: Don't destructure props inside JSX components in Solid projects.
Don't use both children and dangerouslySetInnerHTML props on the same element.
Don't use Array index in keys.
Don't assign to React component props.
Don't define React components inside other components.
Don't use event handlers on non-interactive elements.
Don't assign JSX properties multiple times.
Don't add extra closing tags for components without children.
Use <>...</> instead of ....
Don't insert comments as text nodes.
Don't use the return value of React.render.
Make sure all dependencies are correctly specified in React hooks.
Make sure all React hooks are called from the top level of component functions.
Don't use unnecessary fragments.
Don't pass children as props.
Use semantic elements instead of role attributes in JSX.
Files:
apps/web/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx
**/*.{html,jsx,tsx}
📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)
**/*.{html,jsx,tsx}: Don't use or elements.
Don't use accessKey attribute on any HTML element.
Don't set aria-hidden="true" on focusable elements.
Don't add ARIA roles, states, and properties to elements that don't support them.
Only use the scope prop on elements.
Don't assign non-interactive ARIA roles to interactive HTML elements.
Make sure label elements have text content and are associated with an input.
Don't assign interactive ARIA roles to non-interactive HTML elements.
Don't assign tabIndex to non-interactive HTML elements.
Don't use positive integers for tabIndex property.
Don't include "image", "picture", or "photo" in img alt prop.
Don't use explicit role property that's the same as the implicit/default role.
Make static elements with click handlers use a valid role attribute.
Always include a title element for SVG elements.
Give all elements requiring alt text meaningful information for screen readers.
Make sure anchors have content that's accessible to screen readers.
Assign tabIndex to non-interactive HTML elements with aria-activedescendant.
Include all required ARIA attributes for elements with ARIA roles.
Make sure ARIA properties are valid for the element's supported roles.
Always include a type attribute for button elements.
Make elements with interactive roles and handlers focusable.
Give heading elements content that's accessible to screen readers (not hidden with aria-hidden).
Always include a lang attribute on the html element.
Always include a title attribute for iframe elements.
Accompany onClick with at least one of: onKeyUp, onKeyDown, or onKeyPress.
Accompany onMouseOver/onMouseOut with onFocus/onBlur.
Include caption tracks for audio and video elements.
Make sure all anchors are valid and navigable.
Ensure all ARIA properties (aria-*) are valid.
Use valid, non-abstract ARIA roles for elements with ARIA roles.
Use valid ARIA state and property values.
Use valid values for the autocomplete attribute on input eleme...Files:
apps/web/app/(landing)/welcome/utms.tsxapps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsxapps/web/app/(app)/*/**
📄 CodeRabbit inference engine (.cursor/rules/page-structure.mdc)
Components for the page are either put in page.tsx, or in the apps/web/app/(app)/PAGE_NAME folder
Files:
apps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(app)/*/**/*.tsx
📄 CodeRabbit inference engine (.cursor/rules/page-structure.mdc)
If you need to use onClick in a component, that component is a client component and file must start with 'use client'
Files:
apps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(app)/*/**/**/*.tsx
📄 CodeRabbit inference engine (.cursor/rules/page-structure.mdc)
If we're in a deeply nested component we will use swr to fetch via API
Files:
apps/web/app/(app)/[emailAccountId]/onboarding/page.tsx🧠 Learnings (8)
📓 Common learnings
Learnt from: CR PR: elie222/inbox-zero#0 File: .cursor/rules/llm.mdc:0-0 Timestamp: 2025-08-17T16:57:25.834Z Learning: Applies to apps/web/utils/usage.ts : Implement usage tracking and monitoring in apps/web/utils/usage.ts📚 Learning: 2025-08-17T16:57:25.834Z
Learnt from: CR PR: elie222/inbox-zero#0 File: .cursor/rules/llm.mdc:0-0 Timestamp: 2025-08-17T16:57:25.834Z Learning: Applies to apps/web/utils/usage.ts : Implement usage tracking and monitoring in apps/web/utils/usage.tsApplied to files:
apps/web/app/(landing)/welcome/utms.tsx📚 Learning: 2025-08-17T16:57:25.834Z
Learnt from: CR PR: elie222/inbox-zero#0 File: .cursor/rules/llm.mdc:0-0 Timestamp: 2025-08-17T16:57:25.834Z Learning: Applies to apps/web/utils/{ai,llms}/**/*.ts : Use descriptive scoped loggers per feature and log inputs/outputs with appropriate levels and contextApplied to files:
apps/web/app/(landing)/welcome/utms.tsx📚 Learning: 2025-06-05T09:49:12.168Z
Learnt from: elie222 PR: elie222/inbox-zero#485 File: apps/web/app/(landing)/login/page.tsx:41-43 Timestamp: 2025-06-05T09:49:12.168Z Learning: In Next.js App Router, components that use the `useSearchParams` hook require a Suspense boundary to handle the asynchronous nature of search parameter access. The Suspense wrapper is necessary and should not be removed when a component uses useSearchParams.Applied to files:
apps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx📚 Learning: 2025-07-18T15:04:30.467Z
Learnt from: CR PR: elie222/inbox-zero#0 File: apps/web/CLAUDE.md:0-0 Timestamp: 2025-07-18T15:04:30.467Z Learning: Applies to apps/web/**/*.tsx : Use LoadingContent component for async dataApplied to files:
apps/web/app/(app)/[emailAccountId]/onboarding/page.tsx📚 Learning: 2025-08-10T22:03:30.507Z
Learnt from: elie222 PR: elie222/inbox-zero#667 File: apps/web/app/(app)/[emailAccountId]/onboarding/page.tsx:18-25 Timestamp: 2025-08-10T22:03:30.507Z Learning: In Next.js 15, both `params` and `searchParams` passed to page components in the App Router are Promises that need to be awaited. They should be typed as `Promise<{...}>` and accessed using `await` in server components or React's `use()` hook in client components. This is different from Next.js 14 where they were plain objects.Applied to files:
apps/web/app/(app)/[emailAccountId]/onboarding/page.tsxapps/web/app/(landing)/welcome/page.tsx📚 Learning: 2025-07-20T09:00:16.505Z
Learnt from: CR PR: elie222/inbox-zero#0 File: .cursor/rules/project-structure.mdc:0-0 Timestamp: 2025-07-20T09:00:16.505Z Learning: Applies to apps/web/app/(app)/*/page.tsx : Pages are Server components for direct data loadingApplied to files:
apps/web/app/(landing)/welcome/page.tsx📚 Learning: 2025-07-18T15:07:00.269Z
Learnt from: CR PR: elie222/inbox-zero#0 File: .cursor/rules/page-structure.mdc:0-0 Timestamp: 2025-07-18T15:07:00.269Z Learning: Applies to apps/web/app/(app)/*/page.tsx : Pages are Server components so you can load data into them directlyApplied to files:
apps/web/app/(landing)/welcome/page.tsx🧬 Code graph analysis (3)
apps/web/app/(landing)/welcome/utms.tsx (1)
apps/web/utils/logger.ts (1)
createScopedLogger(17-65)apps/web/app/(app)/[emailAccountId]/onboarding/page.tsx (2)
apps/web/utils/auth.ts (1)
auth(473-474)apps/web/app/(landing)/welcome/utms.tsx (1)
fetchUserAndStoreUtms(7-18)apps/web/app/(landing)/welcome/page.tsx (2)
apps/web/utils/auth.ts (1)
auth(473-474)apps/web/app/(landing)/welcome/utms.tsx (1)
fetchUserAndStoreUtms(7-18)⏰ 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). (1)
- GitHub Check: Analyze (javascript-typescript)
|
Claude finished @elie222's task —— View job PR Review: Fix UTMsI've reviewed the UTM handling implementation across all 4 modified files. Here's my comprehensive feedback: Tasks
📋 SummaryThis PR implements UTM parameter tracking by storing UTM data from cookies into the user database. The changes add UTM collection calls to the onboarding and welcome pages, create a dedicated UTM handling module, and remove UTM-related code from the welcome-redirect page. 🎯 Code Quality & Best Practices✅ Good Practices:
🐛 Potential Bugs & Issues🔴 Critical Issues:
🟡 Minor Issues:
🔒 Security Concerns
Recommendations: // Add validation in utms.tsx
const validateUtmValue = (value: string | undefined): string | undefined => {
if (!value || value.length > 255) return undefined;
// Remove potentially dangerous characters
return value.replace(/[<>\"']/g, '');
};⚡ Performance Considerations✅ Good Performance:
🔄 Potential Optimizations:
🧪 Test Coverage❌ Missing Tests:
Recommended Tests: // Example test cases needed:
describe('UTM Storage', () => {
it('should store valid UTM parameters')
it('should handle missing UTM cookies gracefully')
it('should not overwrite existing UTM data')
it('should sanitize malicious UTM values')
it('should handle database errors gracefully')
})📁 File-Specific Feedback
|
|
Claude finished @elie222's task —— View job PR Review: Fix UTMsI've reviewed the UTM handling implementation across all 4 modified files. Here's my comprehensive feedback: Tasks
📋 SummaryThis PR implements UTM parameter tracking by storing UTM data from cookies into the user database. The changes add UTM collection calls to the onboarding and welcome pages, create a dedicated UTM handling module, and remove UTM-related code from the welcome-redirect page. 🎯 Code Quality & Best Practices✅ Good Practices:
🐛 Potential Bugs & Issues🔴 Critical Issues:
🟡 Minor Issues:
🔒 Security Concerns
Recommendations: // Add validation in utms.tsx
const validateUtmValue = (value: string | undefined): string | undefined => {
if (!value || value.length > 255) return undefined;
// Remove potentially dangerous characters
return value.replace(/[<>\"']/g, '');
};⚡ Performance Considerations✅ Good Performance:
🔄 Potential Optimizations:
🧪 Test Coverage❌ Missing Tests:
Recommended Tests: // Example test cases needed:
describe('UTM Storage', () => {
it('should store valid UTM parameters')
it('should handle missing UTM cookies gracefully')
it('should not overwrite existing UTM data')
it('should sanitize malicious UTM values')
it('should handle database errors gracefully')
})📁 File-Specific Feedback
|
1 participant
Summary by CodeRabbit