Fix valibot import in hono migration docs

[svemat01]

This pull request updates the hono migration documentation to correctly import from valibot instead of zod in the valibot example.

Documentation update:

• In docs/migrate/from-hono.md, replaced the import of zod with valibot in the code example

Summary by CodeRabbit

• Documentation
  • Updated the migration guide to replace the validation library in the Elysia example from Zod to Valibot, aligning the import and example usage with Valibot.
  • Ensured the sample code reflects correct Valibot semantics for consistency.
  • No functional changes to the product; this is a documentation-only update.

[coderabbitai]

Walkthrough

Documentation update in docs/migrate/from-hono.md modifies a code snippet to import and reference Valibot instead of Zod in an Elysia validation example. No functional or API changes.

Changes

Cohort / File(s)	Summary of Changes
Docs — Migration guide docs/migrate/from-hono.md	Updated example import to use Valibot instead of Zod; surrounding snippet unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Replace zod on valibot example #620 — Similar doc-only change switching the validation example import from Zod to Valibot in another migration guide.

Poem

A bunny nibbles docs with care,
Swaps Zod for Valibot—quick flair.
One import hop, the path is clear,
Migration meadow, nothing to fear.
Thump-thump! The guide now feels just right,
Carrots, code, and tidy light. 🥕✨

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 "Fix valibot import in hono migration docs" is a short, single sentence that accurately and concisely describes the primary change in the PR (correcting the Valibot import in the Hono migration documentation), making it clear and relevant for 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

---

📜 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 5e971d8 and 2819547.

📒 Files selected for processing (1)

• docs/migrate/from-hono.md (1 hunks)

🔇 Additional comments (1)

docs/migrate/from-hono.md (1)

343-365: Correct Valibot import — LGTM

import * as v from 'valibot' aligns with the example’s usage (v.object, v.number, v.string). Looks correct.

If the intent is to coerce route params (string → number), confirm whether Elysia auto‑coerces in this context; if not, consider showing Valibot’s coercion utility in the snippet for completeness.

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