#95 and #94 done

[developerEhsan]

Summary by CodeRabbit

• New Features

  • Enhanced clipboard management with new actions to delete and toggle pinned items, making organization easier.
  • Introduced a context menu for improved user interactions.
  • Updated navigation links for a smoother, more intuitive user experience.
  • Added support for pagination and state management in clipboard items.

• Style

  • Polished dark mode aesthetics and overall interface design for a cleaner look.
  • Adjusted note editor responsiveness and removed an outdated note creation button to streamline the layout.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces a series of changes across configuration files, database migration scripts, backend and frontend code, and styling. The updates include restructuring of GitHub labeler definitions and workflows, dependency and metadata updates in package.json, multiple SQL migration scripts with schema modifications, refinements in Drizzle ORM schemas, removal of redundant functions with new IPC handlers for clipboard operations, new clipboard operations utilities, extended preload API types and methods, and significant UI improvements including new context menu and copy widget components.

Changes

Files	Change Summary
.github/labeler.yml, .github/workflows/label.yml, .github/workflows/release.yml, .husky/commit-msg, .vscode/settings.json	Updated CI/CD and commit hook configurations: restructured label definitions (with new changed-files key and renamed labels), added a configuration-path parameter for labeler, removed the release notes generation step, updated commit message validations, and modified spell-checker settings.
package.json	Updated author and repository information, bumped multiple dependency versions, and added a new dependency (@radix-ui/react-context-menu).
resources/database/migrations/* and resources/database/migrations/meta/*	Introduced new and modified SQL migration scripts: added columns, unique indexes, created/renamed tables, and provided new JSON snapshots and journal entries for the SQLite schema.
src/main/drizzle/schema.ts, src/main/index.ts	Enhanced Drizzle ORM schemas by adding a new pinned field, refactored timestamp fields, and added unique constraints; removed the old searchClipboard function and integrated new IPC handlers for deleting and toggling pinned clipboard entries.
src/main/utils/*	Introduced clipboard-operations.ts for search, delete, and toggle pinned functions while simplifying the paste-from-clipboard logic by removing extraneous log lines.
src/preload/*	Extended preload type declarations and added new API methods (togglePinnedClipboardEntry, deleteClipboardEntry) for clipboard management.
src/renderer/src/**/*	Applied various UI updates: added a dark mode CSS variant and a base style layer, updated route URLs, added a new context menu component, refined mutation keys, removed the CreateNoteButton in home view, restructured copy widget state management, and introduced new components (DeleteAction, PinAction, updated WidgetCommandItem) for clipboard entry actions.

Sequence Diagram(s)

sequenceDiagram
  participant UI as Renderer UI
  participant Pre as Preload API
  participant Main as IPC Main
  participant Ops as Clipboard Operations
  participant DB as Database

  UI->>Pre: Invoke delete/toggle action via API
  Pre->>Main: Send IPC message ("delete-clipboard-entry" or "toggle-pinned-clipboard-entry")
  Main->>Ops: Call deleteClipboardEntry or togglePinnedClipboardEntry
  Ops->>DB: Execute DB operation and return result/error
  DB-->>Ops: Send operation result/error
  Ops-->>Main: Return operation outcome
  Main-->>Pre: Return result via IPC
  Pre-->>UI: Update UI with success/error notification

Loading

Possibly related PRs

• Create label.yml #41: Addresses adjustments in the labeler configuration and GitHub Actions workflow, which directly relate to the updated .github/labeler.yml and workflow changes in this PR.

Suggested labels

📄 docs, 🟢 dependencies

Poem

I'm just a rabbit, swift and light,
Hopping through commits in the dead of night.
New labels and workflows set the pace,
Migrations and IPC add grace.
I celebrate these changes with a joyful hop,
Coding merrily until the last bug drops! 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 091987b and 45c68a1.

📒 Files selected for processing (1)

• src/main/utils/clipboard-operations.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.
  • Generate unit testing code for this file.
  • 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. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

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

[coderabbitai]

Actionable comments posted: 4

🧹 Nitpick comments (18)

src/renderer/src/components/home/components/note-editor.tsx (1)

89-89: Enhanced throttling for note updates

Doubling the throttle delay from 1000ms to 2000ms will reduce the frequency of update operations, which could improve performance by decreasing database load, especially during rapid typing or content changes.

Consider adding a comment explaining the reasoning behind this specific delay value and how it balances responsiveness with performance.

src/renderer/src/types/clipboard.ts (2)

6-8: Add documentation for new properties

The new properties will be more maintainable with JSDoc comments explaining their purpose.

 export interface ClipboardDataItem {
   id: number
   type: 'text' | 'file'
   content: string
   createdAt: number
+  /** Current page number when the item is retrieved in paginated results */
   currentPage: number
+  /** Flag indicating whether the clipboard item is pinned */
   pinned: boolean
 }

---

9-14: Add documentation for the new interface

Adding JSDoc comments would improve code maintainability.

+/**
+ * Interface representing paginated clipboard data results
+ */
 export interface ClipboardDataType {
+  /** Array of clipboard items in the current page */
   results: ClipboardDataItem[]
+  /** Total number of clipboard items across all pages */
   total: number
+  /** Total number of pages available */
   totalPages: number
+  /** Current page number */
   currentPage: number
 }

src/preload/index.ts (1)

21-23: Improve type annotations for IPC functions

The current implementation uses generic values and id parameters without specific type annotations, which could lead to type safety issues.

-  togglePinnedClipboardEntry: (values): Promise<void> =>
+  togglePinnedClipboardEntry: (values: { id: number; pinned: boolean }): Promise<void> =>
     ipcRenderer.invoke('toggle-pinned-clipboard-entry', values),
-  deleteClipboardEntry: (id): Promise<void> => ipcRenderer.invoke('delete-clipboard-entry', id)
+  deleteClipboardEntry: (id: number): Promise<void> => ipcRenderer.invoke('delete-clipboard-entry', id)

resources/database/migrations/0009_removed default updatedat value.sql (1)

1-29: Wrap SQL Migration Operations in a Transaction

The migration script clearly disables foreign key constraints, creates new tables, migrates data, drops old tables, and renames new ones. To ensure atomicity and safeguard against partial failures, consider wrapping the entire sequence in a transaction. For example:

+BEGIN TRANSACTION;
 PRAGMA foreign_keys=OFF;--> statement-breakpoint
 CREATE TABLE `__new_clipboard` (
	`id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
	`pinned` integer DEFAULT false NOT NULL,
	`type` text NOT NULL,
	`content` text NOT NULL,
	`createdAt` integer NOT NULL,
	`updatedAt` integer NOT NULL
);
--> statement-breakpoint
 INSERT INTO `__new_clipboard`("id", "pinned", "type", "content", "createdAt", "updatedAt") SELECT "id", "pinned", "type", "content", "createdAt", "updatedAt" FROM `clipboard`;--> statement-breakpoint
 DROP TABLE `clipboard`;--> statement-breakpoint
 ALTER TABLE `__new_clipboard` RENAME TO `clipboard`;--> statement-breakpoint
 PRAGMA foreign_keys=ON;--> statement-breakpoint
 CREATE TABLE `__new_notes` (
	`id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
	`title` text NOT NULL,
	`description` text NOT NULL,
	`favorite` integer DEFAULT false NOT NULL,
	`content` blob NOT NULL,
	`labels` blob,
	`createdAt` integer NOT NULL,
	`updatedAt` integer NOT NULL
);
--> statement-breakpoint
 INSERT INTO `__new_notes`("id", "title", "description", "favorite", "content", "labels", "createdAt", "updatedAt") SELECT "id", "title", "description", "favorite", "content", "labels", "createdAt", "updatedAt" FROM `notes`;--> statement-breakpoint
 DROP TABLE `notes`;--> statement-breakpoint
 ALTER TABLE `__new_notes` RENAME TO `notes`;--> statement-breakpoint
 CREATE UNIQUE INDEX `notes_id_unique` ON `notes` (`id`);
+COMMIT;

Adding a transaction wrapper will help ensure that either all changes are applied or none are, keeping the database in a consistent state.

resources/database/migrations/0008_demonic_shiva.sql (1)

1-18: SQL Migration Atomicity and Data Consistency

This migration script correctly disables foreign key constraints and rebuilds the notes table with the desired schema changes (including a default value for updatedAt). Similar to the previous migration, consider wrapping the entire script in a transaction to ensure atomic updates. Also, verify that the alteration of the clipboard table (adding an updatedAt column) behaves as expected for preexisting rows.

src/renderer/src/assets/main.css (1)

51-58: Global Base Layer Styling Considerations

The new CSS layer declared using @layer base applies global border and outline styles to all elements and sets the background and text colors on the <body>. This can help standardize styling across the application; however, verify that these broad rules do not unintentionally override component-specific styles.

resources/database/migrations/meta/0008_snapshot.json (1)

123-128: Ensure index is properly utilized

The unique index on the id column of the notes table might be redundant since id is already a primary key, which implicitly creates a unique index. This won't cause issues but may be unnecessary.

src/renderer/src/windows/copy-widget/app/components/delete-action.tsx (2)

15-15: Unused prop in interface definition

The inputRef prop is defined in the interface but not included in the component's destructured parameters. However, it is used in the component body. Make sure to include it in the component parameters to maintain consistency.

-export function DeleteAction({ id, currentPage, inputRef }: DeleteActionProps): React.JSX.Element {
+export function DeleteAction({ id, currentPage, inputRef }: DeleteActionProps): React.JSX.Element {

---

67-81: Consider adding error handling for focus operation

When focusing on the input reference after deletion, there's no check to ensure the ref and current property exist before attempting to focus. This could potentially cause errors if the ref is not properly initialized.

-        inputRef.current?.focus()
+        if (inputRef.current) {
+          inputRef.current.focus()
+        }

src/renderer/src/windows/copy-widget/app/components/pin-action.tsx (2)

18-18: Destructured props don't include inputRef

The component receives inputRef in its props interface but doesn't include it in the destructured parameters. If it's not being used in the component, consider removing it from the interface.

-export function PinAction({ id, currentPage, pinned }: PinActionProps): React.JSX.Element {
+export function PinAction({ id, currentPage, pinned, inputRef }: PinActionProps): React.JSX.Element {

Alternatively, if it's truly not needed:

-interface PinActionProps {
-  inputRef: React.RefObject<HTMLInputElement | null>
-  id: number
-  currentPage: number
-  pinned: boolean
-}
+interface PinActionProps {
+  id: number
+  currentPage: number
+  pinned: boolean
+}

---

66-68: Consider updating tooltip text based on current state

For better user experience, consider changing the tooltip text based on the current pinned state (e.g., "Pin to top" or "Unpin").

-      <SimpleTooltip content="Pin to top">
+      <SimpleTooltip content={pinned ? "Unpin" : "Pin to top"}>
        {pinned ? <DrawingPinFilledIcon /> : <DrawingPinIcon />}
      </SimpleTooltip>

src/preload/index.d.ts (1)

80-83: Consider adding a confirm parameter for delete operations

For delete operations, consider adding an optional confirm parameter to allow clients to specify whether a confirmation should be required before deletion, enhancing safety for destructive operations.

-  deleteClipboardEntry: (id: string) => Promise<{
+  deleteClipboardEntry: (id: string, confirm?: boolean) => Promise<{
     result?: string
     error?: unknown
   }>

src/main/utils/clipboard-operations.ts (2)

48-60: Consider using a more specific error type for better error handling.

The function returns a generic unknown error type which makes it difficult for consumers to handle specific error cases.

export async function deleteClipboardEntry(id: string): Promise<{
-  error?: unknown
+  error?: Error
  result?: string
}> {

---

62-86: Consider using a more specific error type here as well.

Similar to the deleteClipboardEntry function, using a generic unknown error type makes error handling more difficult.

export async function togglePinnedClipboardEntry({
  id,
  pinned
}: {
  id: string
  pinned: boolean
}): Promise<{
  result?: string
-  error?: unknown
+  error?: Error
}> {

src/main/index.ts (3)

104-104: Make TODO comment more specific.

The TODO comment lacks specific details about what needs to be done, making it difficult for other developers to understand what's required.

- // TODO - make this workable. Right Now it is not being used
+ // TODO - Make the save-file IPC handler workable. Currently not used in any UI component.

---

142-150: Consider refactoring checkClipboard to use utility functions.

The checkClipboard function directly inserts records into the database instead of using the new utility functions, which could lead to inconsistencies in how clipboard entries are handled.

Consider creating a new utility function in clipboard-operations.ts for creating clipboard entries and use it here.

---

156-156: Add details to the TODO comment.

Similar to the previous TODO comment, this one lacks specific details about what needs to be done.

- // TODO --- This Logic needs to done
+ // TODO --- Implement proper window activation logic for macOS dock icon clicks

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 043964d and 33c8d10.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (34)

• .github/labeler.yml (1 hunks)
• .github/workflows/label.yml (1 hunks)
• .github/workflows/release.yml (0 hunks)
• .husky/commit-msg (3 hunks)
• .vscode/settings.json (1 hunks)
• package.json (5 hunks)
• resources/database/migrations/0007_wild_kronos.sql (1 hunks)
• resources/database/migrations/0008_demonic_shiva.sql (1 hunks)
• resources/database/migrations/0009_removed default updatedat value.sql (1 hunks)
• resources/database/migrations/meta/0007_snapshot.json (1 hunks)
• resources/database/migrations/meta/0008_snapshot.json (1 hunks)
• resources/database/migrations/meta/0009_snapshot.json (1 hunks)
• resources/database/migrations/meta/_journal.json (1 hunks)
• src/main/drizzle/schema.ts (1 hunks)
• src/main/index.ts (5 hunks)
• src/main/utils/clipboard-operations.ts (1 hunks)
• src/main/utils/paste-from-clipboard.ts (0 hunks)
• src/preload/index.d.ts (2 hunks)
• src/preload/index.ts (1 hunks)
• src/renderer/src/assets/main.css (2 hunks)
• src/renderer/src/components/app-sidebar.tsx (1 hunks)
• src/renderer/src/components/home/components/note-editor.tsx (1 hunks)
• src/renderer/src/components/ui/context-menu.tsx (1 hunks)
• src/renderer/src/constants/mutation-keys.ts (1 hunks)
• src/renderer/src/routes/(home)/_home.tsx (2 hunks)
• src/renderer/src/routes/__root.tsx (0 hunks)
• src/renderer/src/store/copy-widget-store.ts (1 hunks)
• src/renderer/src/types/clipboard.ts (1 hunks)
• src/renderer/src/windows/copy-widget/app/components/delete-action.tsx (1 hunks)
• src/renderer/src/windows/copy-widget/app/components/pin-action.tsx (1 hunks)
• src/renderer/src/windows/copy-widget/app/components/rich-text.tsx (1 hunks)
• src/renderer/src/windows/copy-widget/app/components/widget-command-item.tsx (2 hunks)
• src/renderer/src/windows/copy-widget/app/index.tsx (5 hunks)
• src/renderer/src/windows/copy-widget/index.tsx (1 hunks)

💤 Files with no reviewable changes (3)

• src/main/utils/paste-from-clipboard.ts
• src/renderer/src/routes/__root.tsx
• .github/workflows/release.yml

🧰 Additional context used

🪛 Biome (1.9.4)

src/renderer/src/windows/copy-widget/app/components/rich-text.tsx

[error] 15-15: Avoid passing content using the dangerouslySetInnerHTML prop.

Setting content using code can expose users to cross-site scripting (XSS) attacks

(lint/security/noDangerouslySetInnerHtml)

🔇 Additional comments (65)

.vscode/settings.json (1)

11-11: Added "islast" to spell checker dictionary

This addition to the cSpell words will prevent the IDE from flagging "islast" as a spelling error.

src/renderer/src/constants/mutation-keys.ts (1)

4-6:

Details

❓ Verification inconclusive

Added mutation keys for clipboard operations

The new mutation keys for clipboard entry deletion and pinning functionality align with the clipboard management features mentioned in the PR summary.

---

🏁 Script executed:

#!/bin/bash
# Check where these new mutation keys are being used
echo "Searching for usage of delete-clipboard-entry mutation key..."
rg "'delete-clipboard-entry'" --type=tsx --type=ts

echo -e "\nSearching for usage of pinned-clipboard-entry mutation key..."
rg "'pinned-clipboard-entry'" --type=tsx --type=ts

Length of output: 445

---

Below is an updated verification shell script that uses file globs (‑g) instead of relying on the --type flag (which resulted in an error for tsx files). Please re-run this script manually to check for usage of the new keys:

#!/bin/bash
# Re-run search using file globs for TypeScript and TSX files due to errors with the --type flag.
echo "Searching for usage of delete-clipboard-entry mutation key..."
rg "'delete-clipboard-entry'" -g "*.ts" -g "*.tsx"

echo -e "\nSearching for usage of pinned-clipboard-entry mutation key..."
rg "'pinned-clipboard-entry'" -g "*.ts" -g "*.tsx"

Note: The original search produced errors because the file type "tsx" wasn’t recognized with the --type flag. By using the glob filters, you should capture both .ts and .tsx files. Once you confirm that the new mutation keys are used (or not) as expected in the codebase, please update the review status accordingly.

.github/workflows/label.yml (1)

22-22:

Details

✅ Verification successful

Added explicit configuration path for GitHub labeler

This change explicitly defines the path to the labeler configuration file, making the workflow more robust and transparent.

---

🏁 Script executed:

#!/bin/bash
# Verify that the referenced configuration file exists
if [ -f ".github/labeler.yml" ]; then
  echo "✅ Configuration file exists at .github/labeler.yml"
else
  echo "❌ Configuration file NOT found at .github/labeler.yml"
fi

Length of output: 143

---

Configuration file for GitHub Labeler verified

The configuration file exists as expected. No additional changes are needed.

resources/database/migrations/0007_wild_kronos.sql (2)

1-1: Good addition of the pinned feature to clipboard entries.

The addition of the pinned column to the clipboard table with a default value of false and NOT NULL constraint is well-structured. This will enable the pinning functionality mentioned in the mutation keys and copy widget components.

---

2-2: Adding unique constraint to notes.id enhances data integrity.

Creating a unique index on the id column of the notes table is a good database practice. This ensures that all note IDs remain unique and prevents potential data inconsistencies.

src/renderer/src/components/app-sidebar.tsx (1)

29-29: Improved navigation by replacing placeholder URLs with actual routes.

Replacing the placeholder # URLs with actual routing paths (/ and /starred) improves the navigation functionality of the sidebar. This change aligns with the application's new features mentioned in the PR objectives.

Also applies to: 33-33

.husky/commit-msg (2)

1-2: Good practice: Moving commit message validation to a pnpm script.

Moving the commit message validation logic to a pnpm script enhances maintainability and allows for easier updates to the validation logic.

---

56-56: Simplified error messages for better user experience.

Removing "and try again" from the error messages makes them more concise while maintaining clarity about what the user needs to do.

Also applies to: 82-82

src/renderer/src/windows/copy-widget/index.tsx (2)

7-8: Good addition of UI enhancement components.

Adding imports for TooltipProvider and Toaster components is a good step toward enhancing the user interface with tooltips and notifications.

---

14-17: Improved component hierarchy with proper provider wrapping.

The component hierarchy has been properly structured by:

1. Wrapping CopyWidget with TooltipProvider to enable tooltip functionality
2. Adding Toaster as a sibling to provide notification capabilities

This organization follows best practices for React component composition.

src/renderer/src/windows/copy-widget/app/components/rich-text.tsx (2)

2-11: Good performance optimization using useMemo!

The addition of useMemo to cache the innerHtml object is a smart optimization that prevents unnecessary re-renders when the highlighted content hasn't changed.

---

15-15: Consider security implications of dangerouslySetInnerHTML

While the current usage is safe since the HTML content is generated by highlight.js library and not from user input, dangerouslySetInnerHTML can pose XSS risks. Make sure any future modifications maintain this security boundary.

🧰 Tools

🪛 Biome (1.9.4)

[error] 15-15: Avoid passing content using the dangerouslySetInnerHTML prop.

Setting content using code can expose users to cross-site scripting (XSS) attacks

(lint/security/noDangerouslySetInnerHtml)

src/renderer/src/routes/(home)/_home.tsx (1)

35-35:

Details

✅ Verification successful

Simplified component rendering - verify intended behavior

The CreateNoteButton component has been removed from the return statement. Ensure this is intentional and that users can still create notes through another interface element.

---

🏁 Script executed:

#!/bin/bash
# Check if there are other places in the code where users can create notes
rg "createNote|[Cc]reateNote|[Nn]ew [Nn]ote" --type tsx --type ts

Length of output: 95

---

Below is an updated verification script to search for any alternative note creation elements (including “CreateNote”, “CreateNoteButton”, or “New Note”) in both *.tsx and *.ts files:

Once this script runs, please review its output manually to confirm whether another interface element exists that enables note creation. If the output still shows no alternative, it may indicate that removing the CreateNoteButton component requires additional adjustment to preserve functionality.

Action: Verify note creation capability

• Confirm if an alternative UI element or mechanism exists for creating notes elsewhere in the codebase.
• If not, consider whether the removal of CreateNoteButton was intentional or if it needs to be reintroduced.

---

🏁 Script executed:

#!/bin/bash
# Search for note creation components or triggers across .tsx and .ts files
rg -e 'CreateNoteButton|createNote|CreateNote|New Note' --glob '*.tsx' --glob '*.ts'

Length of output: 1526

---

Note Creation UI Verification—Removal of CreateNoteButton Confirmed

The codebase search confirms that note creation functionality now relies on alternative components. Specifically, the output shows:

• Deprecated CreateNoteButton: The CreateNoteButton component (located in src/renderer/src/components/shared/create-note-button.tsx) is marked as deprecated.
• New Note Creation Mechanism: The new CreateNoteModal component (and its corresponding usage in src/renderer/src/components/modals/index.tsx and src/renderer/src/components/modals/create-note-modal.tsx) is actively used to handle note creation via window.api.createNote.

Given that these findings indicate users can still create notes through the updated interface, the removal of the CreateNoteButton from the home route is intentional and does not result in lost functionality.

resources/database/migrations/meta/_journal.json (1)

53-73: Ensure Consistency of New Migration Journal Entries

The new entries (for idx: 7, 8, and 9) are appended with correct timestamps and descriptive tags. Please double-check that the "version" values within these entries (all set to "6") are intentional despite the overall file version being "7". This may be by design but warrants confirmation for consistency across migration records.

src/renderer/src/assets/main.css (1)

3-4: Dark Theme Enhancement for Code Blocks

The addition of the dark-themed highlight.js stylesheet via

@import 'highlight.js/styles/github-dark-dimmed.min.css';

and the definition of a custom variant using

@custom-variant dark (&:is(.dark *));

provide a robust starting point for dark-mode support. Please ensure your build process (or CSS preprocessor) supports the experimental @custom-variant syntax.

resources/database/migrations/meta/0007_snapshot.json (1)

1-138: Database Snapshot Integrity Check

The snapshot effectively captures the schema for both the clipboard and notes tables, including the unique index on notes(id). Note that the clipboard table in this snapshot does not include an updatedAt column, which aligns with its state prior to the 0009_removed default updatedat value.sql migration. Ensure that the snapshot remains in sync with your overall migration history as new schema changes are applied.

resources/database/migrations/meta/0008_snapshot.json (1)

1-146: Confirm dialect and schema compatibility

The schema looks well-structured overall with appropriate column types and constraints. The migration appears to properly capture the addition of the pinned column to the clipboard table as mentioned in the summary.

src/renderer/src/windows/copy-widget/app/components/delete-action.tsx (1)

21-65: Well-implemented mutation with optimistic updates

The mutation implementation is robust, including:

• Proper cancellation of ongoing queries
• Optimistic cache updates for immediate UI feedback
• Snapshot-based state management for potential rollbacks
• Appropriate error and success handling with user notifications

This is a good example of reactive UI design patterns.

src/renderer/src/windows/copy-widget/app/components/pin-action.tsx (1)

22-57: Robust optimistic update implementation

The mutation implementation is well-designed with:

• Proper query cancellation
• State snapshots for potential rollbacks
• Optimistic UI updates that modify both the pinned status and updatedAt timestamp

This ensures a responsive user experience while maintaining data consistency.

src/preload/index.d.ts (2)

10-12: Properties added align with database schema changes

The new properties added to the ClipboardDataItem interface (pinned, updatedAt, and favorite) correctly align with the database schema changes in the migration snapshot, ensuring type safety between the database and frontend.

---

76-83: API methods match component functionality

The new API methods (togglePinnedClipboardEntry and deleteClipboardEntry) provide the necessary backend functionality for the new UI components. The return type structure is consistent with other similar methods in the codebase.

resources/database/migrations/meta/0009_snapshot.json (1)

1-144: Database schema snapshot looks good.

This is a well-structured database schema snapshot for SQLite with proper definitions for both the clipboard and notes tables. The schema follows good practices with appropriate primary keys, data types, and constraints.

src/main/index.ts (2)

127-130: Window state management change is good.

The simplification of the window handling logic by unconditionally minimizing and hiding the copy widget window before pasting is a good approach.

---

138-139: New IPC handlers for clipboard operations look good.

The new handlers for toggling pinned status and deleting clipboard entries are well-integrated with the clipboard operations utility functions.

src/renderer/src/store/copy-widget-store.ts (1)

3-6: Good interface naming improvement.

Changing from PopoverInterface to CopyWidgetState makes the purpose of this interface clearer, and the type change for the open state from boolean to a more specific union type adds flexibility.

src/main/drizzle/schema.ts (2)

7-12: Good refactoring of timestamp fields.

Extracting the createdAt and updatedAt field definitions into reusable constants reduces duplication and improves maintainability. This is a clean approach to DRY (Don't Repeat Yourself) principle in schema definitions.

---

16-16: LGTM - Pinned feature implementation.

The addition of the pinned field with boolean mode and default value of false is correctly implemented. This aligns with the UI changes in the copy widget components.

src/renderer/src/windows/copy-widget/app/components/widget-command-item.tsx (5)

7-13: Clean organization of imports.

The imports are well-organized, bringing in new functionality like formatting date distances and components for delete and pin actions.

---

24-28: Props extension correctly implements new features.

The addition of currentPage and pinned props properly supports the new functionality while maintaining backward compatibility.

---

29-36: Improved state management approach.

Changed from specific popover state to a more generalized state object, making the component more flexible for different states. This is a good architectural improvement.

---

57-77: Enhanced UX with meaningful tooltips.

The implementation of SimpleTooltip improves user experience by providing keyboard shortcut guidance. The icon changes from SearchIcon to TextIcon and ArrowRightIcon to CaretRightIcon provide better visual semantics.

---

90-106: Well-structured detailed view with additional context.

The detailed view now includes useful timestamp information and properly organized action buttons. The layout divides information clearly between item details and actions.

src/renderer/src/windows/copy-widget/app/index.tsx (5)

74-94: Excellent implementation of item sorting logic.

The sorting implementation correctly prioritizes pinned items and then sorts by recency. The code includes proper handling of potential edge cases:

1. Ensures data.pages exists before mapping
2. Properly converts pinned status to numbers for comparison
3. Ensures valid date comparison for updatedAt

This creates a better user experience by making important items more accessible.

---

56-72: Improved keyboard navigation with clear control flow.

The refactored handleKeyDown function improves clarity with explicit element selection checks and better handling of special keys. The navigation now works properly with the detailed view state.

---

108-109: Dynamic positioning based on detail view state.

Smart use of the cn utility to conditionally adjust dialog positioning when the detailed view is open. This creates a better visual flow for the user.

---

131-139: More efficient rendering with composite keys.

Using composite keys (${clipboardData.id}-${clipboardData.createdAt}) for the mapped items ensures proper React reconciliation and prevents potential rendering issues with duplicate IDs.

---

141-149: Improved loading state visibility.

The loading indicator has been enhanced to show a more user-friendly message when there's no more data available. The conditional rendering clearly communicates the application state to users.

src/renderer/src/components/ui/context-menu.tsx (4)

1-39: Well-structured component architecture.

The implementation follows a clean pattern of wrapping Radix UI primitives with additional functionality. Each component is properly typed with React.ComponentProps and includes appropriate data attributes for styling and identification.

---

100-121: Flexible ContextMenuItem with variant support.

The ContextMenuItem implementation includes a variant prop with 'default' and 'destructive' options, enabling contextual styling. The class composition with cn utility properly handles different states and variants.

---

123-171: Accessible checkbox and radio items with clear visual indicators.

Both ContextMenuCheckboxItem and ContextMenuRadioItem components:

1. Implement proper accessibility attributes
2. Include appropriate visual indicators for their state
3. Maintain consistent positioning and styling

This provides a good user experience for selection-based context menus.

---

203-214: Consistent shortcut component for keyboard navigation hints.

The ContextMenuShortcut component provides a standardized way to display keyboard shortcuts within context menu items, with appropriate styling and positioning.

.github/labeler.yml (10)

3-11: Consistency in Label Structure: '🏬 dependencies'

The dependencies label has been renamed to include the "🏬" icon and now nests its file patterns under the changed-files key. This updated structure is clear and consistent with the new labeling approach.

---

12-15: Consistent Refactoring: '🕔 changelog'

The changelog label has been updated to "🕔 changelog" with its file pattern now nested under changed-files. This improves the maintainability and organization of the label configuration.

---

16-22: Enhanced Specificity: '⚡ electron-main'

Renaming the electron main label to "⚡ electron-main" and nesting its file patterns under changed-files aligns well with the new structure.

---

23-29: Uniformity for Renderer Files: 'electron-renderer'

Although the label name remains unchanged, the update to include a nested changed-files structure for renderer-related paths helps maintain consistency. Make sure that the specified patterns fully capture all necessary files for renderer changes.

---

30-37: Well-Structured UI Label: '🎨 ui'

The UI label now correctly nests its file patterns (assets, styles, and CSS directories) under changed-files. This updated organization improves readability.

---

38-50: Comprehensive Build Configuration: '🏗️ build'

The build label now includes an extensive list of configuration files (e.g., webpack, vite, babel, tsconfig, etc.) all nested under changed-files. This should effectively capture all build-related changes.

---

51-59: Streamlined Testing Label: '🧪 tests'

The updates to the testing label correctly nest file patterns for tests and configuration files under changed-files, enhancing clarity.

---

60-66: CI/CD Label Improvement: '🛠️ ci/cd'

Including the .github/labeler.yml file within the changed-files for CI/CD ensures that updates to labeler configuration trigger the appropriate workflows. This is a good update.

---

67-75: Updated Documentation Label: '📄 docs'

The documentation label now neatly groups related files (docs, README, CONTRIBUTING, etc.) under changed-files. This consistent organization is beneficial.

---

76-83: Well-Defined Hotfix Label: '🔥 hotfix'

The hotfix label now nests its file patterns under changed-files, covering source, Electron files, and package.json. This update ensures that hotfix-related changes are easily identifiable.

package.json (14)

6-6: Metadata Update: Author Field

The author field has been updated from "example.com" to "your-ehsan", which accurately reflects the current project ownership.

---

9-12: Enhancement: Repository Field Added

Adding the repository object with the URL and type strengthens the project's metadata and traceability. This change is clear and beneficial.

---

40-40: Dependency Update: @hookform/resolvers

The version for @hookform/resolvers has been incremented to ^4.1.2. This minor update likely includes improvements or fixes. Be sure to test form validations for any potential side effects.

---

44-44: New Dependency: @radix-ui/react-context-menu

The addition of @radix-ui/react-context-menu at ^2.2.6 supports the new context menu components. This inclusion appears appropriate for enhancing UI functionality.

---

62-63: Dependency Updates: @tanstack/react-query & @tanstack/react-router

Both @tanstack/react-query and @tanstack/react-router have been updated to ^5.66.11 and ^1.112.0, respectively. These version bumps should bring improvements or bug fixes. Please verify that these updates integrate smoothly with existing data fetching and routing logic.

---

82-82: Dependency Update: drizzle-orm

Upgrading drizzle-orm to ^0.40.0 may provide performance improvements or new features. Ensure that any changes in the ORM's API are fully compatible with the current database logic.

---

85-85: Dependency Update: lucide-react

The lucide-react dependency has been updated to ^0.477.0. Confirm that all icon components render as expected with this update.

---

102-102: Dev Dependency Update: @tailwindcss/postcss

Upgrading to ^4.0.9 ensures better integration for PostCSS with Tailwind. This update in the development dependencies is straightforward.

---

106-106: Dev Dependency Update: @types/node

Updating @types/node to ^22.13.8 improves type definitions and compatibility with newer Node.js features.

---

112-112: Dev Dependency Update: drizzle-kit

The drizzle-kit version bump to ^0.30.5 should support stable database migrations. Verify that migration commands run without issues post-update.

---

113-113: Dev Dependency Update: electron

The Electron version has been updated to ^34.3.0. It's advisable to test the Electron application thoroughly after this change to catch any regressions.

---

118-118: Dev Dependency Update: eslint-plugin-react-hooks

Upgrading eslint-plugin-react-hooks to ^5.2.0 should enforce improved linting rules around React hooks.

---

126-126: Dev Dependency Update: tailwindcss

The version update to ^4.0.9 likely brings in bug fixes and performance improvements for Tailwind CSS.

---

129-129: Dev Dependency Update: vite

Bumping Vite to ^6.2.0 may improve build times and development experience. It’s important to verify that the build process, including HMR, functions as expected with this update.

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Review the hardcoded timestamp default value

Both the clipboard and notes tables use the same hardcoded timestamp value (1740926069220) as the default for their updatedAt columns. While this works for the initial migration, consider using a dynamic timestamp or NULL and updating it during record creation/modification to avoid future synchronization issues between tables.

Also applies to: 120-120

---

🏁 Script executed:

#!/bin/bash
# Check for similar hardcoded timestamp patterns in other migration files
echo "Checking other migration snapshots for hardcoded timestamps..."
grep -r "default.*17409" --include="*.json" resources/database/migrations/

Length of output: 389

---

Attention: Update Hardcoded Default Timestamps in Migration File

The migration file (resources/database/migrations/meta/0008_snapshot.json) still contains a hardcoded default value (1740926069220) for the updatedAt columns used in both the clipboard and notes tables. The script confirms that this value appears at two locations in the file (lines 52 and 120).

To avoid potential synchronization issues over time, please consider changing this static value to one of the following approaches:

• Use a dynamic timestamp generated at record creation.
• Set the default to NULL and update it during record creation or modification.

[coderabbitai]

⚠️ Potential issue

Be careful with SQL injection in the search function.

The search function directly interpolates the search term into the SQL query, which creates a potential SQL injection vulnerability.

Fix the SQL injection vulnerability by using parameter binding:

- like(clipboardSchema.content, `%${searchTerm}%`),
+ like(clipboardSchema.content, `%` + searchTerm + `%`),

Also make the same change at line 35.

Committable suggestion skipped: line range outside the PR's diff.

[coderabbitai]

⚠️ Potential issue

Fix type mismatch in initial state.

There's a mismatch between the interface definition and the initial state. The CopyWidgetState interface defines opened as 'detailed' | null, but the initial state uses isOpen: false.

- state: { index: 0, isOpen: false },
+ state: { index: 0, opened: null },

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	state: { index: 0, isOpen: false },
	state: { index: 0, opened: null },

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Verify if .unique() is necessary on primary key.

The primary key is already unique by definition. Adding an explicit unique constraint might be redundant, although it doesn't harm functionality.

---

🏁 Script executed:

#!/bin/bash
# Check if SQLite allows unique constraint on primary key and if it creates additional indexes
sqlite3 <<EOF
.mode line
CREATE TABLE test1 (id INTEGER PRIMARY KEY);
CREATE TABLE test2 (id INTEGER PRIMARY KEY UNIQUE);
.schema
.indices
EOF

Length of output: 107

---

Action: Verify the Redundancy of .unique() on Primary Key

The initial shell script using the sqlite3 command failed due to the tool not being available. To further validate the behavior of SQLite regarding primary keys, please run the following Python-based script which uses SQLite’s built-in module:

Review Comment Revision:

The use of .unique() on the primary key column appears redundant since a primary key is inherently unique. Please verify using the above Python test (or confirm manually with your local SQLite instance) that no additional index or constraint is created due to the explicit .unique(). If confirmed, consider removing .unique() to simplify the schema definition.

---

🏁 Script executed:

#!/bin/bash
python3 <<'EOF'
import sqlite3

def get_index_list(create_stmt, table_name):
    conn = sqlite3.connect(':memory:')
    cursor = conn.cursor()
    cursor.execute(create_stmt)
    cursor.execute(f"PRAGMA index_list('{table_name}')")
    indexes = cursor.fetchall()
    print(f"Indexes for {table_name}:", indexes)

print("Testing table with PRIMARY KEY:")
get_index_list('CREATE TABLE test1 (id INTEGER PRIMARY KEY)', 'test1')
print("\nTesting table with PRIMARY KEY UNIQUE:")
get_index_list('CREATE TABLE test2 (id INTEGER PRIMARY KEY UNIQUE)', 'test2')
EOF

Length of output: 167

---

SQLite Confirmation: Remove Redundant Unique Constraint on Primary Key

Our Python-based SQLite test confirms that adding .unique() to a primary key creates an extra auto-index (e.g., sqlite_autoindex_test2_1), even though the primary key already enforces uniqueness. To avoid unintended indexing overhead, please consider removing the explicit .unique() on the primary key in:

• File: src/main/drizzle/schema.ts (line 24)

[coderabbitai]

Actionable comments posted: 0

♻️ Duplicate comments (1)

src/main/utils/clipboard-operations.ts (1)

7-46: ⚠️ Potential issue

Fix SQL injection vulnerability in the count query.

While the search query at line 21 properly uses parameter binding with concatenation ('%' + searchTerm + '%'), the count query at line 35 uses string interpolation (\%${searchTerm}%``), which creates a SQL injection vulnerability.

Apply this fix:

- like(clipboardSchema.content, `%${searchTerm}%`),
+ like(clipboardSchema.content, '%' + searchTerm + '%'),

Additionally, consider extracting the common where clause to reduce duplication:

+ const whereCondition = and(
+   like(clipboardSchema.content, '%' + searchTerm + '%'),
+   between(clipboardSchema.createdAt, fromDate, toDate)
+ );

  const results = await db
    .select()
    .from(clipboardSchema)
    .where(
-     and(
-       like(clipboardSchema.content, '%' + searchTerm + '%'),
-       between(clipboardSchema.createdAt, fromDate, toDate) // Date range filter
-     )
+     whereCondition
    )
    // ...

  const [{ count }] = await db
    .select({ count: sql<number>`COUNT(*)` })
    .from(clipboardSchema)
    .where(
-     and(
-       like(clipboardSchema.content, `%${searchTerm}%`),
-       between(clipboardSchema.createdAt, fromDate, toDate)
-     )
+     whereCondition
    )

🧹 Nitpick comments (3)

src/main/utils/clipboard-operations.ts (3)

48-60: Consider validating the ID parameter before converting to Number.

The deleteClipboardEntry function should validate the ID parameter before conversion to ensure it's a valid number.

export async function deleteClipboardEntry(id: string): Promise<{
  error?: unknown
  result?: string
}> {
  try {
+   if (!id || isNaN(Number(id))) {
+     return { error: 'Invalid ID format' }
+   }
    await db.delete(clipboardSchema).where(eq(clipboardSchema.id, Number(id)))
    return { result: 'success' }
  } catch (error) {
    console.error(error)
    return { error }
  }
}

---

62-86: Consider validating the ID parameter in togglePinnedClipboardEntry.

Similar to the delete function, the toggle function should validate the ID parameter before converting it to a number.

export async function togglePinnedClipboardEntry({
  id,
  pinned
}: {
  id: string
  pinned: boolean
}): Promise<{
  result?: string
  error?: unknown
}> {
  try {
+   if (!id || isNaN(Number(id))) {
+     return { error: 'Invalid ID format' }
+   }
    await db
      .update(clipboardSchema)
      .set({
        pinned,
        updatedAt: Date.now() // Update timestamp
      })
      .where(eq(clipboardSchema.id, Number(id)))
    return { result: 'success' }
  } catch (error) {
    console.error(error)
    return { error }
  }
}

---

1-87: Add feedback for successful/unsuccessful operations.

Consider enhancing the error handling to provide more specific feedback about what went wrong or confirmation about what was done successfully.

For example, the delete function could return:

  try {
    await db.delete(clipboardSchema).where(eq(clipboardSchema.id, Number(id)))
-   return { result: 'success' }
+   return { result: 'Item successfully deleted' }
  } catch (error) {
    console.error(error)
-   return { error }
+   return { error: 'Failed to delete item: ' + (error instanceof Error ? error.message : String(error)) }
  }

Similar improvements could be made to the toggle function.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 33c8d10 and 091987b.

📒 Files selected for processing (2)

• src/main/drizzle/schema.ts (2 hunks)
• src/main/utils/clipboard-operations.ts (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/main/drizzle/schema.ts

🔇 Additional comments (1)

src/main/utils/clipboard-operations.ts (1)

1-5: Good job with the imports organization.

The imports are well-organized, with types first, then local modules, and finally external libraries.