Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughSimplifies NoRules in Rules.tsx by removing its onCreateRule prop and embedded Add button, leaving AddRuleButton in the table header. Enhances SetupContent.tsx with per-step “Mark Done,” localStorage-backed extension install state, adjusted step copy/timing, and layout tweaks. Increments version to v2.9.20. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor User
participant SetupContent
participant StepItem
participant LocalStorage as LocalStorage ("inbox-zero-extension-installed")
rect rgb(240,248,255)
note over SetupContent,StepItem: Extension install step rendering
SetupContent->>SetupContent: isExtensionInstalled = useLocalStorage(key)
SetupContent->>StepItem: showMarkDone=true, onMarkDone=handleMarkExtensionDone
end
User->>StepItem: Click "Mark Done"
activate StepItem
StepItem->>StepItem: handleMarkDone(e) preventDefault/stopPropagation
StepItem-->>SetupContent: onMarkDone()
deactivate StepItem
activate SetupContent
SetupContent->>LocalStorage: set(key, true)
SetupContent-->>SetupContent: state updates (isExtensionInstalled=true)
deactivate SetupContent
SetupContent->>StepItem: Rerender with completed state (check icon)
%% Alternate path: action link navigation
alt User clicks action link
User->>StepItem: Click primary Link
StepItem->>User: Navigate to href
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested reviewers
Pre-merge checks (2 passed, 1 warning)❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
apps/web/app/(app)/[emailAccountId]/setup/SetupContent.tsx (1)
138-141: Row no longer clickable — confirm UX intent.
Previously the whole row linked; now only the right-side action is clickable. If you want to preserve larger hit targets, consider wrapping the left content in a Link as well while keeping the “Mark Done” button separate.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
apps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx(3 hunks)apps/web/app/(app)/[emailAccountId]/setup/SetupContent.tsx(8 hunks)version.txt(1 hunks)
🧰 Additional context used
📓 Path-based instructions (14)
!{.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:
version.txtapps/web/app/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.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:
version.txtapps/web/app/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx
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/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx
apps/web/app/**
📄 CodeRabbit inference engine (apps/web/CLAUDE.md)
NextJS app router structure with (app) directory
Files:
apps/web/app/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.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/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.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/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.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/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx
apps/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]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx
apps/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]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx
apps/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]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.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/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.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/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.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/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.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/(app)/[emailAccountId]/setup/SetupContent.tsxapps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx🧠 Learnings (4)
📚 Learning: 2025-07-19T17:50:22.078Z
Learnt from: CR PR: elie222/inbox-zero#0 File: .cursor/rules/ui-components.mdc:0-0 Timestamp: 2025-07-19T17:50:22.078Z Learning: Applies to components/**/*.tsx : Use the `LoadingContent` component to handle loading statesApplied to files:
apps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx📚 Learning: 2025-07-18T15:05:16.146Z
Learnt from: CR PR: elie222/inbox-zero#0 File: .cursor/rules/fullstack-workflow.mdc:0-0 Timestamp: 2025-07-18T15:05:16.146Z Learning: Applies to apps/web/components/**/*.tsx : Use the `LoadingContent` component to handle loading and error states consistently in data-fetching components.Applied to files:
apps/web/app/(app)/[emailAccountId]/assistant/Rules.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 to handle loading and error states consistentlyApplied to files:
apps/web/app/(app)/[emailAccountId]/assistant/Rules.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]/assistant/Rules.tsx🧬 Code graph analysis (1)
apps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx (1)
apps/web/components/ui/card.tsx (2)
CardHeader(139-139)CardDescription(142-142)⏰ 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: cubic · AI code reviewer
🔇 Additional comments (6)
version.txt (1)
1-1: Version bump looks good.
No functional impact; aligns with PR scope.apps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx (1)
20-20: Import cleanup LGTM.
Removing CardContent and keeping Card/CardHeader/CardDescription matches the simplified empty state.apps/web/app/(app)/[emailAccountId]/setup/SetupContent.tsx (4)
210-218: Local “extension installed” state may desync from progress bar.
completedCount/totalStepscome from the server, while extension completion is client-local. Confirm the extension step isn’t counted server-side; if it is, wire a backend update or adjust the denominator to keep progress accurate.
254-256: Copy/time tweak LGTM.
Shorter estimate and clearer title improve clarity.
281-284: Mark Done wiring for extension looks good.
Event handling prevents navigation; persisted via localStorage.
13-13: Verify dependency: usehooks-ts.
Ensureusehooks-tsis declared in the appropriate package.json (workspace or app). Otherwise builds will fail.Run:
#!/bin/bash # Find all package.json and report usehooks-ts presence and version fd -H package.json | while read -r f; do echo "==> $f" jq -r '[ (.dependencies["usehooks-ts"] // null) as $dep | (.devDependencies["usehooks-ts"] // null) as $dev | {dep:$dep, dev:$dev} ] | .[0]' "$f" done # Quick grep reference rg -n --json '"usehooks-ts"' -- **/package.json
| <NoRules /> | ||
| )} |
There was a problem hiding this comment.
Empty state lost the “Add Rule” CTA — users can’t create a rule when the list is empty.
The Add button only exists in the table header, which isn’t rendered when hasRules is false. Restore a CTA in the empty state.
Apply these diffs:
For the call site:
- <NoRules />
+ <NoRules
+ onCreateRule={onCreateRule}
+ showAddRuleButton={showAddRuleButton}
+ />For the NoRules component:
-function NoRules() {
- return (
- <CardHeader>
- <CardDescription>You don't have any rules yet.</CardDescription>
- </CardHeader>
- );
-}
+function NoRules({
+ onCreateRule,
+ showAddRuleButton = true,
+}: {
+ onCreateRule: () => void;
+ showAddRuleButton?: boolean;
+}) {
+ return (
+ <CardHeader className="flex items-center justify-between">
+ <CardDescription>You don't have any rules yet.</CardDescription>
+ {showAddRuleButton && <AddRuleButton onClick={onCreateRule} />}
+ </CardHeader>
+ );
+}Also applies to: 549-555
🤖 Prompt for AI Agents
In apps/web/app/(app)/[emailAccountId]/assistant/Rules.tsx around lines 492-493
(and similarly 549-555), the empty state currently renders <NoRules /> without
the "Add Rule" CTA so users cannot create rules when the list is empty; update
the call sites to pass an onAdd (or onCreateRule) handler/prop (the same handler
used by the table header Add button) into <NoRules onAdd={...} /> and change the
NoRules component to accept that prop and render a visible, accessible "Add
Rule" button in the empty-state UI that invokes the handler (styled/positioned
to match the header CTA and using the same route or modal logic), ensuring
keyboard accessibility and any existing analytics/event hooks are preserved.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
1 participant
Summary by CodeRabbit