📚 docs: Fix example in whats_new.md

[omer-cengel]

Description

This PR fixes the incorrect custom context example in the whats_new.md documentation. The example was using fiber.Ctx and fiber.NewCtx() which are incorrect - the proper types are fiber.DefaultCtx and fiber.NewDefaultCtx() for embedding in custom context structs.

Fixes #3948

Changes introduced

• Benchmarks: Not applicable
• Documentation Update: Corrected the custom context example in /docs/whats_new.md to use the proper types (fiber.DefaultCtx, fiber.CustomCtx, and fiber.NewDefaultCtx)
• Changelog/What's New: Not applicable
• Migration Guide: Not applicable
• API Alignment with Express: Not applicable
• API Longevity: Not applicable
• Examples: Fixed the example code to demonstrate the correct usage of custom context

Type of change

• Documentation update (changes to documentation)

Checklist

• Conducted a self-review of the code and provided comments for complex or critical parts.
• Updated the documentation in the /docs/ directory for Fiber's documentation.
• Added or updated unit tests to validate the effectiveness of the changes or new features.
• Ensured that new and existing unit tests pass locally with the changes.
• Verified that any new dependencies are essential and have been agreed upon by the maintainers/community.
• Aimed for optimal performance with minimal allocations in the new code.
• Provided benchmarks for the new code to analyze and improve upon.

Commit formatting

Used 📚 Doc: prefix for documentation changes

[coderabbitai]

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

Updated documentation examples to use fiber.DefaultCtx embedding in the CustomCtx struct and adjusted the NewWithCustomCtx factory callback to return fiber.CustomCtx; also a small heading-level formatting change in a routing doc.

Changes

Cohort / File(s)	Summary
Whats new docs docs/whats_new.md	Replaced CustomCtx embedding from fiber.Ctx to fiber.DefaultCtx; changed example NewWithCustomCtx callback to return fiber.CustomCtx; updated initialization from Ctx: *fiber.NewCtx(app) to DefaultCtx: *fiber.NewDefaultCtx(app).
Routing docs (formatting) docs/partials/routing/handler.md	Adjusted heading level from # Use to ## Use (formatting-only change).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Focus review on the docs/whats_new.md code example for accurate types and initialization.
• Verify the handler.md heading change doesn't break included anchors or rendered TOC.

Possibly related PRs

• Add NewWithCustomCtx initialization helper #3476 — Refactor introducing NewWithCustomCtx and switching context handling to DefaultCtx/CustomCtx.
• 🐛 bug: Fix support for context.Context #3720 — Adds Context()/SetContext() behavior to DefaultCtx, affecting how custom contexts interact.
• feat: fiber.Context implement context.Context #3382 — Changes DefaultCtx/Ctx semantics and related example updates that overlap with this doc correction.

Suggested reviewers

• gaby
• sixcolors
• efectn

Poem

🐇 I hopped through docs to mend the mix,
Swapped Ctx for DefaultCtx — a neat little fix.
CustomCtx now stands tall and true,
Examples tidy, readers too.
🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'docs: Fix example in whats_new.md' clearly and specifically describes the main change—fixing a documentation example—and accurately reflects the changeset.
Description check	✅ Passed	The description provides clear context, references the linked issue, documents changes with appropriate checkboxes, specifies the type of change, and includes a relevant checklist.
Linked Issues check	✅ Passed	The PR successfully addresses issue #3948 by correcting the custom context example to use fiber.CustomCtx and fiber.DefaultCtx instead of incorrect types.
Out of Scope Changes check	✅ Passed	Besides the main documentation fix, there is a minor formatting change to a heading in routing/handler.md, which appears to be a tangential documentation improvement rather than out-of-scope.
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

---

📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 293d8af and 30ea6c7.

📒 Files selected for processing (1)

• docs/partials/routing/handler.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• docs/partials/routing/handler.md

---

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 @omer-cengel, 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 addresses and rectifies an inaccuracy within the whats_new.md documentation. Specifically, it corrects the example demonstrating custom context usage in Fiber, ensuring that the provided code snippets utilize the proper types (fiber.DefaultCtx and fiber.NewDefaultCtx()) for embedding within custom context structs. This enhancement improves the reliability and clarity of the documentation, guiding users toward correct implementation patterns.

Highlights

• Documentation Correction: Updated the custom context example in whats_new.md to use the correct fiber.DefaultCtx and fiber.NewDefaultCtx() types, replacing the previously incorrect fiber.Ctx and fiber.NewCtx() usages.
• Example Code Fix: Modified the fiber.NewWithCustomCtx function's return type in the example from fiber.Ctx to fiber.CustomCtx, ensuring the example accurately reflects custom context implementation.

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 correctly fixes an example for using custom contexts in the whats_new.md documentation. The changes replace incorrect types and function calls with the correct ones. My review includes a suggestion to further improve the example by making it more complete and demonstrating the usage of the custom context, which would enhance its value for developers.

[gaby]

@omer-cengel Markdownlint failure is unrelated, but can you fix that here too. Thanks!

[welcome]

Congrats on merging your first pull request! 🎉 We here at Fiber are proud of you! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord