Skip to content

Simplify examples list#741

Merged
elie222 merged 1 commit intomainfrom
feat/simplify-examples
Sep 2, 2025
Merged

Simplify examples list#741
elie222 merged 1 commit intomainfrom
feat/simplify-examples

Conversation

@elie222
Copy link
Owner

@elie222 elie222 commented Sep 2, 2025

Summary by CodeRabbit

  • New Features

    • Introduced an Examples panel that lets you insert suggested prompts directly into the editor.
    • Support for passing custom example sets per selection/persona.
  • UI/UX

    • Examples panel now appears alongside the editor when available.
    • Button label updated to “Choose from examples.”
    • Reduced editor and loading skeleton height for a more compact layout.
  • Changes

    • Examples panel hidden in the older Rules view.
  • Chores

    • Version bumped to v2.7.9.

@vercel
Copy link

vercel bot commented Sep 2, 2025

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

Project Deployment Preview Updated (UTC)
inbox-zero Ready Ready Preview Sep 2, 2025 8:28pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 2, 2025

Walkthrough

Introduces an optional examples array into the examples pipeline: components accept and pass examples to getExamplePrompts(provider, examples). RulesPromptNew renders an always-visible Examples panel (when examples exist) that inserts selections into the editor. RulesPrompt comments out the old Examples rendering. Version bumped to v2.7.9.

Changes

Cohort / File(s) Summary
Examples data plumbing
apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx, apps/web/app/(app)/[emailAccountId]/assistant/examples.ts
ExamplesList now requires an examples: string[] prop and forwards it to getExamplePrompts(provider, examples). getExamplePrompts signature updated to accept optional examples and use them if provided; otherwise falls back to defaults.
RulesPrompt (legacy) UI toggle
apps/web/app/(app)/[emailAccountId]/assistant/RulesPrompt.tsx
The Examples component rendering is commented out; UI no longer mounts Examples even when showExamples is true. Callback remains but is unused.
RulesPromptNew integration
apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.tsx
Replaces personaPrompt string with examples array flow. Always shows an Examples panel when examples exist; selecting an example inserts it into the editor. Adjusted layout, labels, and sizing.
Version
version.txt
Bumped version from v2.7.8 to v2.7.9.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor User
  participant RulesPromptNew as RulesPromptNew
  participant Examples as ExamplesList
  participant Editor as Rules Editor
  participant Utils as getExamplePrompts()

  Note over RulesPromptNew: Mount with provider and persona.examples
  RulesPromptNew->>Examples: Render with {provider, examples[]}
  Examples->>Utils: getExamplePrompts(provider, examples[])
  Utils-->>Examples: Prompt list (processed)
  Examples-->>RulesPromptNew: Display example items

  User->>Examples: Click example
  Examples-->>RulesPromptNew: onSelect(example)
  RulesPromptNew->>Editor: Insert trimmed example text
  Editor-->>User: Updated content
Loading
sequenceDiagram
  autonumber
  actor User
  participant RulesPrompt (old)
  participant Examples (old)

  Note over RulesPrompt: Examples rendering is commented out
  User->>RulesPrompt: Toggle showExamples
  RulesPrompt--x Examples: No mount (commented)
  Note over User,RulesPrompt: Examples UI not available in this flow
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested reviewers

  • edulelis

Poem

A bunny taps the keys—hop, hop—
New examples flow, no need to stop.
Prompts now plucked with gentle care,
Into the editor—trimmed and fair.
Old pane sleeps, new pane shines,
v2.7.9—ear-twitching lines! 🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/simplify-examples

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, please upgrade to Bugbot Pro by visiting the Cursor dashboard. Your first 14 days will be free!

const personaPrompt = persona
? personas[persona as keyof typeof personas]?.prompt
const examples = persona
? personas[persona as keyof typeof personas].promptArray
Copy link

Choose a reason for hiding this comment

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

Bug: Optional Chaining Removed Causing Runtime Errors

It looks like the optional chaining operator (?.) was removed when accessing personas[persona as keyof typeof personas].promptArray. If persona isn't a valid key, this could lead to a runtime error trying to access promptArray on an undefined value, where the previous code would have safely returned undefined.

Fix in Cursor Fix in Web

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

🧹 Nitpick comments (3)
apps/web/app/(app)/[emailAccountId]/assistant/examples.ts (1)

70-77: Clarify fallback when an empty examples array is passed.
Using examples || examplePromptsBase treats [] as truthy, yielding no prompts. If you intend to fall back when examples is empty, switch to a length check.

Apply:

-export function getExamplePrompts(
-  provider: string,
-  examples?: string[],
-): string[] {
-  return processPromptsWithTerminology(
-    examples || examplePromptsBase,
-    provider,
-  );
-}
+export function getExamplePrompts(
+  provider: string,
+  examples?: string[],
+): string[] {
+  const source = examples && examples.length > 0 ? examples : examplePromptsBase;
+  return processPromptsWithTerminology(source, provider);
+}
apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx (1)

10-16: Ensure buttons don’t submit forms if embedded later.
Guidelines require a type on buttons. These buttons could be placed within a form in future usages.

Outside this hunk, update the Example button:

-              <Button
+              <Button
+                type="button"
                 key={example}
                 variant="outline"
                 onClick={() => onSelect(example)}
                 className="h-auto w-full justify-start text-wrap py-2 text-left"
               >

Also applies to: 20-20

apps/web/app/(app)/[emailAccountId]/assistant/RulesPrompt.tsx (1)

347-349: Commented Examples block is now outdated (prop change).
If you re-enable it, Examples now requires an examples prop. Also, addExamplePrompt is currently unused.

Consider:

-{/* {showExamples && (
-  <Examples onSelect={addExamplePrompt} provider={provider} />
-)} */}
+{/* {showExamples && (
+  <Examples
+    examples={personas.other.promptArray}
+    onSelect={addExamplePrompt}
+    provider={provider}
+  />
+)} */}

Or remove addExamplePrompt until this block is restored.

📜 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.

📥 Commits

Reviewing files that changed from the base of the PR and between 1398e01 and f581d72.

📒 Files selected for processing (5)
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx (1 hunks)
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPrompt.tsx (1 hunks)
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.tsx (5 hunks)
  • apps/web/app/(app)/[emailAccountId]/assistant/examples.ts (1 hunks)
  • version.txt (1 hunks)
🧰 Additional context used
📓 Path-based instructions (15)
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]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/examples.ts
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.tsx
apps/web/app/**

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

NextJS app router structure with (app) directory

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/examples.ts
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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/app/(app)/[emailAccountId]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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/(app)/[emailAccountId]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/examples.ts
  • version.txt
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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/app/(app)/[emailAccountId]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/examples.ts
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/examples.ts
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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/(app)/[emailAccountId]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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/app/(app)/[emailAccountId]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/examples.ts
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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/(app)/[emailAccountId]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/examples.ts
  • version.txt
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.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]/assistant/RulesPrompt.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx
  • apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.tsx
**/*.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/app/(app)/[emailAccountId]/assistant/examples.ts
🧬 Code graph analysis (1)
apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.tsx (3)
apps/web/app/(app)/[emailAccountId]/assistant/create/examples.tsx (1)
  • examples (13-144)
apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx (1)
  • Examples (55-55)
apps/web/components/editor/SimpleRichTextEditor.tsx (1)
  • SimpleRichTextEditor (28-158)
⏰ 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: Cursor Bugbot
🔇 Additional comments (9)
version.txt (1)

1-1: Version bump looks good.
No functional impact here.

apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx (1)

10-16: Type is fine; consider defensive fallback.
examples: string[] is required and you already gate rendering upstream. If you ever relax that, pass a non-empty array to avoid rendering nothing.

Would you like me to add a tiny guard here to default to base prompts when examples.length === 0?

Also applies to: 20-20

apps/web/app/(app)/[emailAccountId]/assistant/RulesPromptNew.tsx (7)

42-44: Persona → examples mapping looks correct.
Good use of promptArray to drive the Examples panel.


51-53: Prop threading LGTM.
Passing examples into RulesPromptForm keeps the flow clean.


68-75: Props shape update looks consistent.
Optional examples?: string[] aligns with conditional rendering paths.


150-157: Examples panel integration looks good; ensure child is client.
This relies on ExamplesList.tsx being a Client Component. Add "use client" there (see comment in that file).


182-182: Skeleton height reduction acknowledged.
No UX concerns; matches editor height change.


187-187: Editor height reduced to 180.
Confirm readability on smaller screens; otherwise fine.


201-202: Copy update reads better.
“Choose from examples” is clearer for users.

Comment on lines +10 to 16
examples,
onSelect,
provider,
className = "mt-1.5 sm:h-[60vh] sm:max-h-[60vh]",
}: {
examples: string[];
onSelect: (example: string) => void;
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Mark this component as a Client Component.
This file defines interactive UI (onClick) and is imported by Client Components. Add the "use client" directive to avoid Next.js RSC import errors.

Add at the very top of the file:

"use client";

Also applies to: 20-20

🤖 Prompt for AI Agents
In apps/web/app/(app)/[emailAccountId]/assistant/ExamplesList.tsx around lines
10-16 (and also line 20), this component uses interactive handlers and is
imported by Client Components but lacks the Next.js Client Component directive;
add the "use client" directive as the very first line of the file (before any
imports or code) to mark it as a client component and prevent RSC import errors.

@elie222 elie222 merged commit 24d7ee3 into main Sep 2, 2025
19 checks passed
@elie222 elie222 deleted the feat/simplify-examples branch September 2, 2025 20:43
@coderabbitai coderabbitai bot mentioned this pull request Nov 5, 2025
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

Comments