📒 docs: clarify client migration examples

[ReneWerner87]

Summary

• highlight client configuration improvements in the v3 "What's New" guide with an example showing default options and request overrides
• expand the client migration guide with before/after snippets for shared defaults, body handling, and path/query parameters

Testing

• make audit (fails: govulncheck unable to fetch vulnerabilities due to 403 Forbidden)
• make generate
• make betteralign
• make modernize
• make format
• make lint
• make test (fails: Test_App_BodyLimit_Zero timed out)

---

Codex Task

[coderabbitai]

Warning

Rate limit exceeded

@ReneWerner87 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 26 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 64eb643 and cec3908.

📒 Files selected for processing (1)

• docs/whats_new.md (2 hunks)

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Added a "Configuration improvements" section to docs/whats_new.md describing centralized client defaults with per-request overrides, five migration patterns, and before/after examples for headers/timeouts, body handling, path/query helpers, agent helpers, and top-level client helpers (documentation-only change).

Changes

Cohort / File(s)	Change Summary
Documentation Updates docs/whats_new.md	Added "Configuration improvements" under Client: documents centralized client defaults with per-request overrides, five common migration patterns (shared defaults, body handling, path/query helpers, agent helpers, fiber-level client helpers), and multiple before/after code examples and migration guidance.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Verify accuracy and clarity of migration examples and code snippets
• Ensure terminology aligns with existing client configuration docs
• Confirm no accidental API claims or behavioral changes are stated

Suggested reviewers

• gaby
• sixcolors
• efectn

Poem

🐰 I hopped through pages, tidy and bright,

Defaults set snug, per-call just right,
Examples dancing, migrations in view,
I nibble a carrot and say, "All anew!" 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change as documentation updates to client migration examples, which aligns with the changeset focused on clarifying client configuration and migration patterns.
Description check	✅ Passed	The description covers the main changes (client configuration improvements and migration guide expansion) and testing steps, but lacks detail on migration guidance and examples as specified in the template.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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

[gemini-code-assist]

Summary of Changes

Hello @ReneWerner87, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the documentation for the Fiber v3 client. It clarifies the new centralized configuration capabilities and provides practical migration examples for developers transitioning from older client usage patterns. The changes aim to make it easier for users to understand and adopt the improved client features, ensuring a smoother development experience.

Highlights

• Client Configuration Documentation: The 'What's New' guide for v3 has been updated to highlight client configuration improvements, including an example demonstrating how to set default options and override them per request using client.Config.
• Client Migration Examples: The client migration guide has been expanded with detailed 'before' and 'after' code snippets for common migration scenarios, such as handling shared defaults, body serialization, and path/query parameters.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request enhances the documentation by adding several clear and helpful examples for client migration from v2 to v3. The new sections in docs/whats_new.md effectively demonstrate configuration improvements and common migration patterns. I have one suggestion to improve an example for consistency and to better promote best practices.

[Copilot]

Pull request overview

This PR enhances the v3 migration documentation by adding comprehensive client configuration examples and before/after code snippets to help developers transition from v2 to v3.

• Adds a "Configuration improvements" section demonstrating centralized client configuration with per-request overrides
• Provides three detailed migration patterns covering shared defaults, body handling, and path/query parameters
• Includes practical code examples showing v2 patterns alongside their v3 equivalents

[ReneWerner87]

/gemini review

[gemini-code-assist]

Code Review

This pull request clarifies client migration examples in the documentation, which is a great improvement for users upgrading to v3. The new examples in whats_new.md clearly demonstrate the configuration improvements and common migration patterns. My review focuses on ensuring the code examples are not only clear but also follow best practices. I've pointed out a few places where response objects should be closed to prevent resource leaks, which is a critical practice to teach in examples.