Update cookie secret comment in migration guide

[WaveringAna]

Clarified comment about cookie secret in Elysia setup.

Summary by CodeRabbit

• Documentation
  • Enhanced migration guide with clarified instructions on cookie secret configuration for proper cookie signing.

[coderabbitai]

Walkthrough

Documentation was updated in the Hono-to-Elysia migration guide to add a clarifying comment to the cookie example, explaining that the secret parameter must be configured to enable cookie signing functionality.

Changes

Cohort / File(s)	Summary
Documentation updates docs/migrate/from-hono.md	Added explanatory comment to cookie signing example clarifying that the secret must be set to enable cookie signing

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Minor documentation clarification with no code logic changes

Poem

🐰 A secret whispered in the docs so bright,
Where cookies now wear hats of clarified light,
No code was shifted, just wisdom unfurled,
One gentle comment makes the migration world!

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 accurately summarizes the main change: updating a cookie secret comment in the migration documentation guide.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

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

1065-1065: Clarify the comment for better user understanding.

The comment "// Need to set to have cookies signed" is helpful, but consider being more explicit about the implications. Users may benefit from knowing this is a required configuration step.

Consider updating the comment to be slightly more descriptive:

- secret: 'secret' // Need to set to have cookies signed
+ secret: 'secret' // Required to enable automatic cookie signing

Alternatively, if you want to keep it concise, the current phrasing works but "must be set" is slightly clearer than "need to set":

- secret: 'secret' // Need to set to have cookies signed
+ secret: 'secret' // Must be set to enable cookie signing

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9449e74 and 83be906.

📒 Files selected for processing (1)

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

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

docs/migrate/from-hono.md

1065-1065: Hard tabs
Column: 1

(MD010, no-hard-tabs)

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix indentation: replace hard tab with spaces.

The static analysis tool flagged a hard tab character at the beginning of this line. Markdown files should use spaces for indentation to maintain consistency.

Replace the hard tab with spaces to align indentation with the rest of the code block.

- [TAB]secret: 'secret' // Need to set to have cookies signed
+ [SPACES]secret: 'secret' // Need to set to have cookies signed

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

🧰 Tools

🪛 markdownlint-cli2 (0.18.1)

1065-1065: Hard tabs
Column: 1

(MD010, no-hard-tabs)

🤖 Prompt for AI Agents

In docs/migrate/from-hono.md around line 1065, the line beginning with a hard
tab ("		secret: 'secret' // Need to set to have cookies signed") uses a tab for
indentation; replace the leading tab character with the appropriate number of
spaces to match the surrounding code block indentation (use spaces consistently,
e.g., two or four spaces as used elsewhere in that block) so the file no longer
contains hard tabs.