Skip to content

Conversation

@dantesCode
Copy link

@dantesCode dantesCode commented Nov 5, 2025

I've noticed that in the "From other frameworks?" section of each comparison card, multiple descriptions are repeated.

Summary by CodeRabbit

Documentation

  • Fixed comparison descriptions to correctly identify source frameworks in migration guides, ensuring accurate documentation for users transitioning from Express or Hono.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 5, 2025

Walkthrough

This PR corrects documentation text in the table of contents file. Two comparison card descriptions that incorrectly referenced "tRPC" now properly reference the correct source frameworks: "Express" and "Hono" respectively.

Changes

Cohort / File(s) Change Summary
Documentation text corrections
docs/table-of-content.md
Updated "From Express" card from "Comparison between tRPC and Elysia" to "Comparison between Express and Elysia" and updated "From Hono" card from "Comparison between tRPC and Elysia" to "Comparison between Hono and Elysia"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

  • Simple text corrections with no logic, structural, or control flow changes

Possibly related PRs

Poem

🐰 A typo caught in the table's embrace,
Where tRPC wore the wrong framework's face,
Now Express and Hono shine bright and clear,
In their rightful place, for all to see here!

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Fix repeated description' directly addresses the main issue: correcting duplicate/repeated comparison descriptions in the documentation's framework comparison cards.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3bb29b8 and ee5b5ff.

📒 Files selected for processing (1)
  • docs/table-of-content.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
docs/table-of-content.md

82-82: Hard tabs
Column: 1

(MD010, no-hard-tabs)


83-83: Hard tabs
Column: 1

(MD010, no-hard-tabs)


85-85: Hard tabs
Column: 3

(MD010, no-hard-tabs)


88-88: Hard tabs
Column: 3

(MD010, no-hard-tabs)

🔇 Additional comments (1)
docs/table-of-content.md (1)

81-89: Correct fixes for repeated descriptions.

The changes properly correct the duplicated "tRPC" descriptions in the "From Express" and "From Hono" comparison cards. Lines 82 and 88 now accurately reflect their respective source frameworks.

<Deck>
<Card title="From Express" href="/migrate/from-express">
Comparison between tRPC and Elysia
Comparison between Express and Elysia
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Replace hard tabs with spaces.

Markdownlint flags hard tabs (MD010) at these locations. For consistency with markdown linting standards and to ensure proper rendering across environments, replace the tabs with spaces.

Also applies to: 83-83, 85-85, 88-88

🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

82-82: Hard tabs
Column: 1

(MD010, no-hard-tabs)

🤖 Prompt for AI Agents
In docs/table-of-content.md around lines 82, 83, 85 and 88, replace all hard tab
characters with spaces to satisfy MD010: convert each tab to spaces while
preserving existing indentation and alignment (use a consistent width, e.g., 2
or 4 spaces per tab across the file), save the file and re-run markdownlint to
confirm the warnings are resolved.

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