Reviewing files that changed from the base of the PR and between a8f7288 and fe2e63b.

• apps/web/app/(ee)/api/customers/count/route.ts (2 hunks)
• apps/web/app/(ee)/api/customers/route.ts (2 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/earnings/page-client.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/earnings/page.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/layout.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/page-client.tsx (0 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/page.tsx (0 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/sales/page-client.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/sales/page.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/commissions/commission-table.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/earnings/page-client.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/earnings/page.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/layout.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/sales/page-client.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/sales/page.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/page-client.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/page.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/partners/[partnerId]/partner-nav.tsx (3 hunks)
• apps/web/lib/middleware/utils/app-redirect.ts (1 hunks)
• apps/web/lib/zod/schemas/customers.ts (1 hunks)
• apps/web/ui/analytics/use-analytics-filters.tsx (1 hunks)
• apps/web/ui/customers/customer-activity-list.tsx (1 hunks)
• apps/web/ui/customers/customer-details-column.tsx (4 hunks)
• apps/web/ui/customers/customer-partner-earnings-table.tsx (5 hunks)
• apps/web/ui/customers/customer-sales-table.tsx (4 hunks)
• apps/web/ui/customers/customer-stats.tsx (1 hunks)
• apps/web/ui/customers/customer-table/customer-table.tsx (7 hunks)
• apps/web/ui/customers/customer-tabs.tsx (1 hunks)
• apps/web/ui/layout/page-nav-tabs.tsx (1 hunks)
• apps/web/ui/layout/sidebar/app-sidebar-nav.tsx (1 hunks)
• apps/web/ui/partners/fraud-risks/commissions-on-hold-table.tsx (1 hunks)
• apps/web/ui/partners/fraud-risks/fraud-events-tables/fraud-matching-customer-email-table.tsx (1 hunks)
• apps/web/ui/partners/fraud-risks/fraud-events-tables/fraud-paid-traffic-detected-table.tsx (1 hunks)
• packages/ui/src/timestamp-tooltip.tsx (1 hunks)

• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/page.tsx
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/page-client.tsx

• GitHub Check: build

apps/web/ui/layout/sidebar/app-sidebar-nav.tsx (1)

290-294: LGTM!

The new "Customers" navigation item is correctly placed in the program insights section and follows the established patterns. The UserCheck icon is properly imported, and the route /${slug}/program/customers aligns with the PR's objective to introduce program-scoped customer pages.

Based on learnings, this incremental approach to updating routes (prioritizing visible navigation first) is consistent with your preferred workflow.

packages/ui/src/timestamp-tooltip.tsx (1)

151-152: Good semantic HTML structure.

The explicit <tbody> wrapper properly structures the table according to HTML5 standards.

apps/web/ui/customers/customer-activity-list.tsx (1)

120-122: LGTM!

The addition of rounded-lg improves visual consistency with the loading state and other card-based UI components in the customer details flow.

apps/web/lib/zod/schemas/customers.ts (1)

41-41: LGTM!

The programId field follows the established pattern for optional filter parameters and is correctly inherited by getCustomersCountQuerySchema for consistent filtering across endpoints.

apps/web/app/(ee)/api/customers/count/route.ts (1)

36-40: Verify behavior for customers without links.

The nested link: { programId } filter will exclude customers with linkId: null. If this is the intended behavior for program-scoped views (only showing customers acquired through program links), this looks correct.

apps/web/ui/analytics/use-analytics-filters.tsx (1)

766-770: LGTM!

The permalink update correctly aligns with the new program-scoped routing structure (/{slug}/program/customers/...), maintaining consistency with the broader route restructuring in this PR.

apps/web/ui/customers/customer-partner-earnings-table.tsx (2)

36-41: LGTM!

Cell renderers are appropriately simplified to concise single-line arrow functions.

---

79-79: LGTM!

Padding and layout updates improve visual consistency with the rest of the table UI.

Also applies to: 96-96, 107-119

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/sales/page-client.tsx (2)

22-22: Verify redirect behavior during render.

Using redirect() during the render phase is valid in Next.js App Router but throws an exception to interrupt rendering. Ensure this doesn't cause issues with any parent error boundaries or Suspense boundaries.

---

45-55: LGTM!

Smart optimization to conditionally fetch total sales count only when the initial data reaches the limit, avoiding unnecessary API calls.

apps/web/ui/layout/page-nav-tabs.tsx (2)

72-104: LGTM!

The tab rendering with animated selection indicator using motion is well-implemented. The pathname.endsWith() approach for selection detection is reasonable for the controlled tab IDs used in this context.

---

108-133: LGTM!

QuickLinks section is cleanly implemented with external link indicators and proper target handling.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/partners/[partnerId]/partner-nav.tsx (1)

5-5: LGTM! Clean refactoring to shared PageNavTabs component.

The refactoring successfully consolidates the inline navigation logic into the reusable PageNavTabs component, reducing code duplication and improving maintainability. The quicklinks → quickLinks rename also improves naming consistency.

Also applies to: 15-15, 62-62, 81-86

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/sales/page.tsx (1)

1-5: LGTM! Follows the standard page/page-client separation pattern.

This wrapper correctly delegates to the client component for data fetching and rendering, which is the expected Next.js pattern for this type of page structure.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/sales/page.tsx (1)

1-5: LGTM! Consistent with the established page wrapper pattern.

This follows the same clean separation pattern used in the non-program-scoped sales page, maintaining consistency across the routing structure.

apps/web/ui/customers/customer-sales-table.tsx (1)

61-61: LGTM! UI polish improves table spacing and formatting.

The padding updates (p-2 → px-4 py-3) provide better vertical and horizontal spacing, and the simplified amount cell formatting using currencyFormatter directly is cleaner than the previous implementation.

Also applies to: 108-108, 125-125, 136-140

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/page.tsx (1)

1-20: LGTM! Well-structured page with helpful user guidance.

The page composition is clean, using appropriate layout wrappers and providing clear context through the title and help link. The separation of concerns between the page wrapper and client component is well executed.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/earnings/page.tsx (1)

1-5: LGTM! Follows the consistent page wrapper pattern.

Clean implementation that maintains consistency with the other customer detail pages.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/earnings/page.tsx (1)

1-5: LGTM! Consistent wrapper implementation.

This completes the consistent page structure pattern across all customer detail pages (both general and program-scoped).

apps/web/app/(ee)/api/customers/route.ts (1)

48-48: [Rewritten review comment]
[Classification tag]

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/page-client.tsx (1)

6-14: LGTM!

The component correctly wires up the program-scoped customer table by passing defaultProgramId from the workspace context and setting isProgramPage to enable program-specific behavior. The use of || undefined properly handles falsy values for the query parameter.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/layout.tsx (2)

40-106: Well-structured layout implementation.

The two-column responsive grid with proper ordering, loading states, and activity section is cleanly organized. The conditional rendering for customer name skeleton and the activity list integration follow good UX patterns.

---

37-38: Consider handling the loading state before redirecting.

The redirect fires immediately when customerError.status === 404, but if workspaceSlug is still loading (undefined), this could redirect to /undefined/customers. Consider adding a guard:

-  if (customerError && customerError.status === 404)
-    redirect(`/${workspaceSlug}/customers`);
+  if (customerError && customerError.status === 404 && workspaceSlug)
+    redirect(`/${workspaceSlug}/customers`);

⛔ Skipped due to learnings

Learnt from: steven-tey
Repo: dubinc/dub PR: 2958
File: apps/web/app/app.dub.co/(dashboard)/[slug]/settings/members/page-client.tsx:432-457
Timestamp: 2025-10-15T01:05:43.266Z
Learning: In apps/web/app/app.dub.co/(dashboard)/[slug]/settings/members/page-client.tsx, defer refactoring the custom MenuItem component (lines 432-457) to use the shared dub/ui MenuItem component to a future PR, as requested by steven-tey.

Learnt from: TWilson023
Repo: dubinc/dub PR: 2736
File: apps/web/lib/swr/use-bounty.ts:11-16
Timestamp: 2025-08-26T15:05:55.081Z
Learning: In the Dub codebase, workspace authentication and route structures prevent endless loading states when workspaceId or similar route parameters are missing, so gating SWR loading states on parameter availability is often unnecessary.

apps/web/ui/customers/customer-tabs.tsx (1)

8-47: Clean tab navigation implementation.

The conditional tab rendering based on customer's program association and the dynamic basePath for program vs non-program contexts are well-implemented. The useMemo dependencies correctly track the relevant customer properties.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/earnings/page-client.tsx (1)

73-82: Guard SWR key against undefined workspaceId.

The non-null assertion workspaceId! will cause the API call to be made with workspaceId=undefined as a string if the workspace hasn't loaded yet. Consider guarding the SWR key:

  const { data: commissions, isLoading: isComissionsLoading } = useSWR<
    CommissionResponse[]
  >(
-    `/api/commissions?${new URLSearchParams({
+    workspaceId &&
+      `/api/commissions?${new URLSearchParams({
        customerId,
-       workspaceId: workspaceId!,
+       workspaceId,
        pageSize: CUSTOMER_PAGE_EVENTS_LIMIT.toString(),
      })}`,
    fetcher,
  );

⛔ Skipped due to learnings

Learnt from: TWilson023
Repo: dubinc/dub PR: 2736
File: apps/web/lib/swr/use-bounty.ts:11-16
Timestamp: 2025-08-26T15:05:55.081Z
Learning: In the Dub codebase, workspace authentication and route structures prevent endless loading states when workspaceId or similar route parameters are missing, so gating SWR loading states on parameter availability is often unnecessary.

Learnt from: TWilson023
Repo: dubinc/dub PR: 2538
File: apps/web/ui/partners/overview/blocks/commissions-block.tsx:16-27
Timestamp: 2025-06-18T20:26:25.177Z
Learning: In the Dub codebase, components that use workspace data (workspaceId, defaultProgramId) are wrapped in `WorkspaceAuth` which ensures these values are always available, making non-null assertions safe. This is acknowledged as a common pattern in their codebase, though not ideal.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/sales/page-client.tsx (1)

13-32: LGTM! Clean component structure with proper data fetching.

The component correctly uses useCustomer hook with enriched fields and handles the loading/not-found states. The redirect pattern for missing customers after loading is appropriate.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/layout.tsx (2)

20-38: LGTM! Data fetching and error handling look correct.

The component properly chains data fetching (workspace → customer → activity) and handles the 404 case with a redirect. The conditional SWR key for activity ensures the request only fires when customer data is available.

---

40-107: Well-structured layout with proper loading states.

The responsive grid layout with loading skeletons and proper composition of child components follows good patterns. The isCustomerActivityLoading prop correctly accounts for both customer loading and activity loading states.

apps/web/ui/customers/customer-table/customer-table.tsx (1)

71-77: LGTM! Clean prop interface for the table component.

The updated function signature properly types the query prop using the Zod schema inference and provides sensible defaults.

apps/web/ui/customers/customer-details-column.tsx (4)

42-65: Clean pattern for rendering basic fields with loading states.

The basicFields array pattern with conditional inclusion based on customer data provides a clean way to handle the email/country display with proper loading skeletons.

---

198-212: LGTM! Proper program-aware path construction for analytics links.

The isProgramPage conditional correctly adjusts the analytics path to include /program/ when viewing from the program context.

---

258-301: Well-structured referral section with partner support.

The referral section cleanly handles three states: loading, with partner, and without partner. The conditional rendering and link construction are correct.

---

306-314: LGTM! Clean helper component for detail headings.

The DetailHeading component provides consistent styling for section headings throughout the details column.

apps/web/ui/partners/fraud-risks/commissions-on-hold-table.tsx (1)

90-90: LGTM: Customer link updated to program scope.

The update to the program-scoped customer path is consistent with the PR's routing restructure.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/commissions/commission-table.tsx (1)

162-162: LGTM: Customer link correctly scoped to program context.

Since this table is already in the program context (/program/commissions/), the program-scoped customer path is the appropriate choice.

apps/web/ui/partners/fraud-risks/fraud-events-tables/fraud-matching-customer-email-table.tsx (1)

75-75: LGTM: Fraud event customer link updated to program scope.

The program-scoped path is appropriate for fraud detection features.

apps/web/ui/partners/fraud-risks/fraud-events-tables/fraud-paid-traffic-detected-table.tsx (2)

87-87: LGTM: Customer link updated to program scope.

The program-scoped path aligns with the fraud detection feature context.

---

87-87: Add redirect rules for old customer paths and deprecate or remove old routes.

The path update is correct, but migration is incomplete. Both old (/${slug}/customers/) and new (/${slug}/program/customers/) routes are currently active with fully functional pages. Configure redirects from old customer paths to new program paths, or remove the old route files. Without redirects, bookmarks and incoming links to the old path will break.

Reviewing files that changed from the base of the PR and between fe2e63b and efb8fab.

• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/layout.tsx (1 hunks)
• apps/web/lib/middleware/utils/app-redirect.ts (1 hunks)
• apps/web/ui/customers/customer-table/customer-table.tsx (7 hunks)

• GitHub Check: build

apps/web/lib/middleware/utils/app-redirect.ts (1)

84-98: LGTM! Previous issues resolved.

The customer redirect rules are correctly implemented and follow the established pattern from the partner redirect above. The comments accurately describe the behavior (previous typo concerns about "partnerId" have been fixed), and the regex patterns appropriately validate that customer IDs start with "cus_" before redirecting to the sales subpage.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/layout.tsx (1)

66-102: Layout structure and props look good.

The isProgramPage prop is now correctly passed to both CustomerDetailsColumn (line 72) and CustomerTabs (line 77), ensuring proper program-page URL construction. Loading states are appropriately propagated to child components.

apps/web/ui/customers/customer-table/customer-table.tsx (6)

7-9: LGTM!

The new imports are necessary for the program-scoped functionality: getCustomersQuerySchema for typing the query prop, PartnerRowItem for the partner column, and z for type inference.

---

53-61: LGTM!

Adding "partner" to the available columns while keeping it out of defaultVisible is appropriate since the partner column is only conditionally rendered on program pages.

---

71-77: LGTM!

The props interface uses schema inference for type safety, and isProgramPage defaulting to false maintains backward compatibility with existing usages.

---

138-150: LGTM!

The conditional routing based on isProgramPage correctly directs users to program-scoped or workspace-scoped customer detail pages.

---

282-283: LGTM!

The dependency array now correctly includes both isProgramPage and workspaceSlug, addressing the stale closure concern from the previous review.

---

99-114: LGTM!

The query prop is correctly propagated to both useCustomersCount and the SWR fetch, enabling proper filtering for program-scoped views.

Reviewing files that changed from the base of the PR and between efb8fab and 9606a45.

• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/layout.tsx (1 hunks)
• apps/web/ui/customers/customer-table/customer-table.tsx (7 hunks)

• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/layout.tsx

• GitHub Check: build

apps/web/ui/customers/customer-table/customer-table.tsx (2)

158-161: All previous review feedback addressed! ✅

Great work addressing the prior review comments:

• The debug console.log statement has been removed
• workspaceSlug is now included in the useMemo dependency array (line 285)
• The partner column now has a proper null guard (lines 158-161)

Also applies to: 285-285

---

71-77: LGTM: Clean component API extension.

The new props are well-typed using Zod schema inference, and the isProgramPage default ensures backward compatibility for existing usages.

Reviewing files that changed from the base of the PR and between 20fe549 and 63a4d2a.

• apps/web/app/(ee)/partners.dub.co/(dashboard)/programs/[programSlug]/(enrolled)/customers/[customerId]/page-client.tsx (2 hunks)
• apps/web/app/(ee)/partners.dub.co/(dashboard)/programs/[programSlug]/(enrolled)/customers/[customerId]/page.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/layout.tsx (1 hunks)
• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/layout.tsx (1 hunks)
• apps/web/ui/customers/customer-details-column.tsx (4 hunks)
• apps/web/ui/customers/customer-stats.tsx (1 hunks)

• apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/customers/[customerId]/layout.tsx

• GitHub Check: build

apps/web/app/(ee)/partners.dub.co/(dashboard)/programs/[programSlug]/(enrolled)/customers/[customerId]/page-client.tsx (1)

78-142: Clean responsive layout structure.

The two-column responsive layout using @container queries is well-structured. The order swapping (@3xl/page:order-1 and @3xl/page:order-2) ensures appropriate visual hierarchy across viewport sizes.

apps/web/app/(ee)/partners.dub.co/(dashboard)/programs/[programSlug]/(enrolled)/customers/[customerId]/page.tsx (1)

1-5: LGTM!

Clean simplification. Moving the layout wrappers into page-client.tsx keeps this server component as a thin shell while consolidating rendering logic in the client component.

apps/web/ui/customers/customer-details-column.tsx (2)

246-251: Inconsistent fallback behavior between analytics and UTM links.

The UTM parameter links only render when workspaceSlug is present (line 248), while the analytics links above (line 207) fall back to /programs/${programSlug}/ when workspaceSlug is undefined. Is this intentional? Consider whether UTM links should also support the program-slug fallback for consistency.

---

300-313: LGTM! Clear fallback logic for referral links.

The conditional href construction appropriately handles both workspace (direct link) and program (analytics query) contexts, with a sensible fallback to undefined when neither is available.

apps/web/app/app.dub.co/(dashboard)/[slug]/(ee)/program/customers/[customerId]/layout.tsx (2)

37-38: Past review issues have been resolved.

The 404 redirect now correctly targets the program-scoped customers route (line 38), and isProgramPage is properly passed to CustomerTabs (line 78). These changes address the previous review feedback.

Also applies to: 78-78

---

89-92: This link to the workspace events page is correct. Events are aggregated at the workspace level in the application, not scoped per-program. There is no program-level events page to navigate to, and the same link pattern is used consistently across both program and non-program customer layouts.

Likely an incorrect or invalid review comment.

Reviewing files that changed from the base of the PR and between 63a4d2a and 6eaeae3.

• apps/web/lib/middleware/utils/app-redirect.ts (1 hunks)

• GitHub Check: build

Reviewing files that changed from the base of the PR and between 6eaeae3 and cbf5fe2.

• apps/web/app/(ee)/partners.dub.co/(dashboard)/programs/[programSlug]/(enrolled)/customers/[customerId]/page-client.tsx (2 hunks)
• apps/web/lib/swr/use-partner-customer.ts (1 hunks)
• apps/web/ui/customers/customer-details-column.tsx (4 hunks)

• GitHub Check: build

apps/web/app/(ee)/partners.dub.co/(dashboard)/programs/[programSlug]/(enrolled)/customers/[customerId]/page-client.tsx (2)

10-14: LGTM! Clean import additions for layout refactoring.

The new imports for PageContent, PageWidthWrapper, icons, and formatDate are all appropriately used in the refactored component structure.

---

78-142: LGTM! Well-structured responsive layout refactoring.

The two-column grid layout is well-implemented with:

• Proper responsive breakpoints and column sizing
• Correct order manipulation for different screen sizes
• All business logic preserved (reward eligibility, period warnings, loading states)
• Clean separation of CustomerDetailsColumn, Earnings, and Activity sections

The refactoring successfully maintains functionality while improving the page structure.

apps/web/ui/customers/customer-details-column.tsx (6)

27-42: LGTM: Props correctly support program/workspace routing contexts.

The addition of isProgramPage and workspaceSlug props properly enables the component to generate correct URLs for both workspace-scoped and partner-scoped contexts. The type change to CustomerEnriched aligns with the enriched data structure.

---

44-67: LGTM: Elegant conditional field collection.

The basicFields array construction intelligently handles different states:

• Email field included during loading (shows skeleton) or when present
• Email field excluded when customer exists without email
• Country field always present with sensible fallback

The pattern cleanly separates field definition from rendering logic.

---

204-208: LGTM: URL construction correctly implements business rules.

The href logic properly handles both workspace and partner contexts. Based on the established architectural constraint that isProgramPage is only true when workspaceSlug is defined, the URL patterns generated are:

• Workspace program: /${workspaceSlug}/program/analytics?...
• Workspace non-program: /${workspaceSlug}/analytics?...
• Partner-side: /programs/${programSlug}/analytics?...

This aligns with the route structure clarified in the previous review discussion.

Based on learnings: TWilson023 confirmed that all program pages have workspaceSlug available, ensuring the conditional logic here is sound.

---

238-263: LGTM: UTM parameter handling is clean and consistent.

The UTM section:

• Only renders when parameters exist (line 238)
• Correctly limits analytics links to workspace context (line 248)
• Uses the same sound URL construction pattern as device/browser/OS links

The grid layout efficiently displays parameter labels and values while handling overflow properly.

---

266-319: LGTM: Partner and referral link handling is well-structured.

The section correctly adapts to different contexts:

• Partner information (lines 272-291): Renders partner avatar and name with link when in workspace context
• Referral link routing (lines 302-307): Appropriately distinguishes between:
  • Workspace: Direct link to full link detail page
  • Partner-side: Analytics page with domain/key filters

The different routing approaches make sense given partner users likely have restricted access to link detail pages.

---

84-332: LGTM: Clean card-based layout with excellent loading state handling.

The refactored component structure provides:

• Clear visual hierarchy with the new card container
• Consistent skeleton loading states throughout (lines 96, 118, 130, 149, 218, 296)
• Responsive grid layouts that adapt to different viewport sizes
• Improved semantic HTML with DetailHeading using h3 instead of h2 (line 328)

The modular organization with distinct sections (avatar, basic fields, details, UTM, referral) makes the component easy to maintain and extend.

apps/web/lib/swr/use-partner-customer.ts (1)

13-15: The current implementation is correct and should not be changed. The API endpoint conditionally adds the name field to the response based on customerDataSharingEnabledAt, so the field is not always present. Updating PartnerProfileCustomerSchema to unconditionally include name would misrepresent the API contract. The frontend's type intersection PartnerProfileCustomerProps & { name?: string | null } correctly reflects that the field may or may not be present in the response.

Likely an incorrect or invalid review comment.