Skip to content

Comments

Premium expired sidebar card#816

Merged
elie222 merged 2 commits intomainfrom
feat/premium-expired-card
Sep 25, 2025
Merged

Premium expired sidebar card#816
elie222 merged 2 commits intomainfrom
feat/premium-expired-card

Conversation

@elie222
Copy link
Owner

@elie222 elie222 commented Sep 25, 2025

Summary by CodeRabbit

  • New Features

    • Added a Premium Expired banner with dismiss and “Reactivate” CTA; now shown in the sidebar.
  • Refactor

    • Removed the old premium alert from the Automation and Cold Email Blocker pages to avoid duplicate messaging.
  • Documentation

    • Added showcase scenarios for various premium-expired states on the landing components page.
  • Chores

    • Bumped app version to v2.10.18.

@vercel
Copy link

vercel bot commented Sep 25, 2025

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

Project Deployment Preview Updated (UTC)
inbox-zero Ready Ready Preview Sep 25, 2025 0:44am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 25, 2025

Caution

Review failed

The pull request is closed.

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

Removed PremiumAlert usage from two app pages, added a new PremiumExpiredCard component (and presentational variant), rendered it in SideNav and landing examples, and bumped version to v2.10.18.

Changes

Cohort / File(s) Summary of changes
Remove PremiumAlert usage
apps/web/app/(app)/[emailAccountId]/automation/page.tsx, apps/web/app/(app)/[emailAccountId]/cold-email-blocker/page.tsx
Deleted PremiumAlert/PremiumAlertWithData imports and JSX usage; pages now render their main content without that alert.
Landing examples for premium states
apps/web/app/(landing)/components/page.tsx
Added PremiumExpiredCardContent imports and multiple scenario blocks to showcase expired/active premium states (duplicated section).
New premium expiration banner component
apps/web/components/PremiumExpiredCard.tsx
Added PremiumExpiredCard and PremiumExpiredCardContent: normalize premium data, derive premium state, map subscription statuses to messages, optional dismiss handling, and “Reactivate” CTA linking to /settings.
SideNav integration
apps/web/components/SideNav.tsx
Imported and rendered <PremiumExpiredCard /> inside SideNav between main content and footer.
Version bump
version.txt
Updated version from v2.10.17 to v2.10.18.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant U as User
  participant App as Web App
  participant SideNav as SideNav
  participant Banner as PremiumExpiredCard
  participant UserSvc as useUser/Auth
  participant Content as PremiumExpiredCardContent
  participant Settings as /settings

  U->>App: Navigate
  App->>SideNav: Render
  SideNav->>Banner: Mount
  Banner->>UserSvc: fetch user & premium
  UserSvc-->>Banner: return user + premium

  alt no data or user premium or dismissed
    Banner-->>SideNav: no render
  else expired/inactive
    Banner->>Content: render with status
    Content-->>SideNav: show banner + Reactivate CTA
    U->>Content: Click Reactivate
    Content->>Settings: Navigate to /settings
    U->>Content: (optional) Click Dismiss
    Content->>Banner: onDismiss()
    Banner-->>SideNav: hide banner
  end
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

Suggested reviewers

  • edulelis

Poem

I nibble code and polish the yard,
A banner blooms where alerts were hard.
“Reactivate” — I thump, I hop, I cheer,
Off to settings, the path is clear.
Carrots, banners, a tidy trail — hip hop, hooray! 🥕🐇

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 title succinctly captures the core update of adding a premium-expired status card to the sidebar without extraneous details, making the main change immediately clear to reviewers.

📜 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 d3b14a4 and ff144f9.

📒 Files selected for processing (1)
  • apps/web/components/PremiumExpiredCard.tsx (1 hunks)

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: 2

📜 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 fedf472 and d3b14a4.

📒 Files selected for processing (6)
  • apps/web/app/(app)/[emailAccountId]/automation/page.tsx (0 hunks)
  • apps/web/app/(app)/[emailAccountId]/cold-email-blocker/page.tsx (0 hunks)
  • apps/web/app/(landing)/components/page.tsx (2 hunks)
  • apps/web/components/PremiumExpiredCard.tsx (1 hunks)
  • apps/web/components/SideNav.tsx (2 hunks)
  • version.txt (1 hunks)
💤 Files with no reviewable changes (2)
  • apps/web/app/(app)/[emailAccountId]/automation/page.tsx
  • apps/web/app/(app)/[emailAccountId]/cold-email-blocker/page.tsx
🧰 Additional context used
📓 Path-based instructions (12)
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/components/SideNav.tsx
  • apps/web/components/PremiumExpiredCard.tsx
  • apps/web/app/(landing)/components/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
Use result?.serverError with toastError and toastSuccess
Use LoadingContent component to handle loading and error states consistently
Pass loading, error, and children props to LoadingContent

Files:

  • apps/web/components/SideNav.tsx
  • apps/web/components/PremiumExpiredCard.tsx
  • apps/web/app/(landing)/components/page.tsx
apps/web/components/**/*.tsx

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

Use React Hook Form with Zod validation for form handling

Use the LoadingContent component to handle loading and error states consistently in data-fetching components.

Use PascalCase for components (e.g. components/Button.tsx)

Files:

  • apps/web/components/SideNav.tsx
  • apps/web/components/PremiumExpiredCard.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/components/SideNav.tsx
  • apps/web/components/PremiumExpiredCard.tsx
  • apps/web/app/(landing)/components/page.tsx
  • version.txt
**/*.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/components/SideNav.tsx
  • apps/web/components/PremiumExpiredCard.tsx
  • apps/web/app/(landing)/components/page.tsx
**/*.{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/components/SideNav.tsx
  • apps/web/components/PremiumExpiredCard.tsx
  • apps/web/app/(landing)/components/page.tsx
**/*.{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/components/SideNav.tsx
  • apps/web/components/PremiumExpiredCard.tsx
  • apps/web/app/(landing)/components/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/components/SideNav.tsx
  • apps/web/components/PremiumExpiredCard.tsx
  • apps/web/app/(landing)/components/page.tsx
  • version.txt
**/*.{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/components/SideNav.tsx
  • apps/web/components/PremiumExpiredCard.tsx
  • apps/web/app/(landing)/components/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/components/SideNav.tsx
  • apps/web/components/PremiumExpiredCard.tsx
  • apps/web/app/(landing)/components/page.tsx
apps/web/app/**

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

NextJS app router structure with (app) directory

Files:

  • apps/web/app/(landing)/components/page.tsx
apps/web/app/**/*.tsx

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

Components with onClick must be client components with use client directive

Files:

  • apps/web/app/(landing)/components/page.tsx
🧬 Code graph analysis (3)
apps/web/components/SideNav.tsx (1)
apps/web/components/PremiumExpiredCard.tsx (1)
  • PremiumExpiredCard (147-164)
apps/web/components/PremiumExpiredCard.tsx (2)
apps/web/utils/premium/index.ts (1)
  • isPremium (14-22)
apps/web/utils/index.ts (1)
  • cn (4-6)
apps/web/app/(landing)/components/page.tsx (1)
apps/web/components/PremiumExpiredCard.tsx (1)
  • PremiumExpiredCardContent (25-145)
⏰ 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: Vercel Agent Review
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
version.txt (1)

1-1: Version bump acknowledged

Matches the new feature set—no issues spotted.

apps/web/app/(landing)/components/page.tsx (1)

385-458: Showcase scenarios look comprehensive

Great coverage of the various premium states; this will help future regressions surface quickly.

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 6 files

Prompt for AI agents (all 1 issues)

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


<file name="apps/web/components/PremiumExpiredCard.tsx">

<violation number="1" location="apps/web/components/PremiumExpiredCard.tsx:157">
Passing a hard-coded premium object forces the expired banner for all users. Use the actual user.premium (allow null/undefined) so the card renders only when the subscription is inactive.</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 e7e7e45 into main Sep 25, 2025
8 of 10 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Nov 14, 2025
@elie222 elie222 deleted the feat/premium-expired-card branch December 18, 2025 23:04
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