Added Mac pasting shorcut to legend.

[PEPOAFONSO]

Added a very simple tweak to the legend so it shows the mac shortcut.

Summary by CodeRabbit

• Style
  • Updated the paste instruction on the home page to display “CTRL+V or CMD+V,” clarifying the shortcut for Windows/Linux and macOS users.
  • Improves clarity and reduces confusion for Mac users without altering any functionality or layout.
  • No behavioral changes; purely a copy update to the on-screen guidance for pasting content.

[coderabbitai]

Walkthrough

Updated UI text in src/pages/index.vue to display paste instruction as "CTRL+V or CMD + V" instead of only "CTRL+V". No structural or logic changes.

Changes

Cohort / File(s)	Summary of Changes
UI copy update src/pages/index.vue	Modified displayed instruction text to include both CTRL+V and CMD + V. No functional code changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title concisely and accurately describes the primary change—adding the Mac paste shortcut to the legend—and aligns with the PR description and the single-line UI text modification in src/pages/index.vue, so it communicates the main intent to reviewers.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b535618 and d4f22aa.

📒 Files selected for processing (1)

• src/pages/index.vue (1 hunks)

🔇 Additional comments (1)

src/pages/index.vue (1)

37-37: Mac shortcut added — LGTM

Good UX improvement to mention macOS.

[coderabbitai]

⚠️ Potential issue

Avoid hard‑coded English; use i18n like the title/subtitle

This string bypasses Vue I18n used elsewhere in the file.

Apply this diff to localize the key labels while keeping the gradient:

-      Use the <code class="text-transparent bg-clip-text bg-gradient-to-br from-rose-400 to-fuchsia-600">CTRL+V or CMD + V</code>
+      Use the <code class="text-transparent bg-clip-text bg-gradient-to-br from-rose-400 to-fuchsia-600">{{ t('index.pasteKeys', { ctrl: 'Ctrl+V', cmd: 'Cmd+V' }) }}</code>

Follow‑up: add index.pasteKeys to your locale files, e.g., "index.pasteKeys": "{ctrl} or {cmd}".

📝 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

	Use the <code class="text-transparent bg-clip-text bg-gradient-to-br from-rose-400 to-fuchsia-600">CTRL+V or CMD + V</code>
	Use the <code class="text-transparent bg-clip-text bg-gradient-to-br from-rose-400 to-fuchsia-600">{{ t('index.pasteKeys', { ctrl: 'Ctrl+V', cmd: 'Cmd+V' }) }}</code>

🤖 Prompt for AI Agents

In src/pages/index.vue around line 37, the hard‑coded "CTRL+V or CMD + V" string
bypasses Vue I18n; replace the literal content with a call to
$t('index.pasteKeys', { ctrl: 'CTRL+V', cmd: 'CMD + V' }) (or the component
equivalent) so the gradient-wrapped code element remains but its inner text
comes from i18n, and add an index.pasteKeys entry to your locale files like
"{ctrl} or {cmd}" so translations can substitute the placeholders.

---

🛠️ Refactor suggestion

Use semantic for keyboard keys and fix spacing/casing

Improves a11y and consistency: “Ctrl+V” / “Cmd+V” (no spaces around +).

Option A (no i18n change):

-      Use the <code class="text-transparent bg-clip-text bg-gradient-to-br from-rose-400 to-fuchsia-600">CTRL+V or CMD + V</code>
+      Use the <span class="text-transparent bg-clip-text bg-gradient-to-br from-rose-400 to-fuchsia-600"><kbd>Ctrl</kbd>+<kbd>V</kbd> or <kbd>Cmd</kbd>+<kbd>V</kbd></span>

Option B (with i18n variable for the keys):

-      Use the <code class="text-transparent bg-clip-text bg-gradient-to-br from-rose-400 to-fuchsia-600">CTRL+V or CMD + V</code>
+      Use the <span class="text-transparent bg-clip-text bg-gradient-to-br from-rose-400 to-fuchsia-600">{{ t('index.pasteKeys', { ctrl: 'Ctrl+V', cmd: 'Cmd+V' }) }}</span>

📝 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

	Use the <code class="text-transparent bg-clip-text bg-gradient-to-br from-rose-400 to-fuchsia-600">CTRL+V or CMD + V</code>
	Use the <span class="text-transparent bg-clip-text bg-gradient-to-br from-rose-400 to-fuchsia-600"><kbd>Ctrl</kbd>+<kbd>V</kbd> or <kbd>Cmd</kbd>+<kbd>V</kbd></span>

🤖 Prompt for AI Agents

In src/pages/index.vue around line 37, the inline key hint currently uses a code
element with inconsistent spacing and casing; replace it with semantic <kbd>
elements and normalize to "Ctrl+V" and "Cmd+V" (no spaces around the plus and
capitalized as shown). Wrap each key token in its own <kbd> element (e.g.,
<kbd>Ctrl</kbd>+<kbd>V</kbd> / <kbd>Cmd</kbd>+<kbd>V</kbd>), and optionally move
the key strings into i18n variables if you need localized control over
platform-specific labels.