Update tutorial.md

[mjjabarullah]

Summary by CodeRabbit

• Documentation
  • Updated tutorial cards to accurately describe comparisons.
    • “From Express” now says “Comparison between Express and Elysia.”
    • “From Hono” now says “Comparison between Hono and Elysia.”
  • Improves clarity for readers evaluating or migrating from Express or Hono to Elysia, reducing confusion with previous tRPC wording.
  • Text-only updates; no functional or API changes.

[coderabbitai]

Walkthrough

Updated documentation text in docs/tutorial.md: two Card descriptions now reference comparisons with Express and Hono versus Elysia, replacing prior mentions of tRPC. No code or API changes.

Changes

Cohort / File(s)	Summary
Docs: tutorial copy tweaks docs/tutorial.md	Updated Card text: “From Express” → “Comparison between Express and Elysia”; “From Hono” → “Comparison between Hono and Elysia”. No functional changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled on docs with delicate care,
Swapped tRPC crumbs for Express and Hono flair.
No code to chase, no bugs to scare—
Just tidy trails in the tutorial lair.
Thump-thump! The guide reads light as air. 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title "Update tutorial.md" correctly indicates a documentation file was changed but is overly generic and does not summarize the substantive edit (the tutorial's comparison cards were updated to reference Express and Hono vs Elysia instead of tRPC), so it does not clearly convey the main change to reviewers.	Please use a more descriptive title such as "Clarify tutorial comparisons: replace tRPC with Express and Hono" or "Update tutorial card comparisons to Express/Hono vs Elysia" so the primary change is immediately clear.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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: 0

🧹 Nitpick comments (1)

docs/tutorial.md (1)

49-58: Replace hard tabs with spaces (markdownlint MD010)

Lines 51, 52, 54, and 57 contain tabs. Convert to spaces to satisfy markdownlint and keep indentation consistent.

Apply:

-		Comparison between Express and Elysia
+        Comparison between Express and Elysia
-  		Comparison between Fastify and Elysia
+        Comparison between Fastify and Elysia
-  		Comparison between Hono and Elysia
+        Comparison between Hono and Elysia

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a69c128 and 2cf6f1b.

📒 Files selected for processing (1)

• docs/tutorial.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

docs/tutorial.md

51-51: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

52-52: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

54-54: Hard tabs
Column: 3

(MD010, no-hard-tabs)

---

57-57: Hard tabs
Column: 3

(MD010, no-hard-tabs)

🔇 Additional comments (3)

docs/tutorial.md (3)

51-52: Copy tweak LGTM

“Comparison between Express and Elysia” reads correctly and matches the card’s link.

---

57-58: Copy tweak LGTM

“Comparison between Hono and Elysia” is clear and consistent with the link.

---

49-58: Resolved — target migration pages exist

Both /migrate/from-express and /migrate/from-hono are present (docs/migrate/from-express.md, docs/migrate/from-hono.md); the cards will not 404.