docs: Make Handle errors section up to date with API #6456
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Stanislav (Stanley) Modrak <44023416+smith558@users.noreply.github.com>
metcoder95
reviewed
Jan 22, 2026
Member
There was a problem hiding this comment.
Can you fix the linting issues?
Contributor
Author
I will asap. Busy this week. Feel free to edit PR if needed, though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the “Handle errors” section of the Hitchhiker’s Guide to reflect Fastify’s current public API.
The previous text described
after()as supporting callbacks with up to three parameters, which reflects historical / Avvio-internal behaviour but is no longer part of Fastify’s documented or typed API. Today,fastify.after()supports either:The updated section removes references to unsupported callback arities, aligns the documentation with the current typings and behaviour, and keeps the guidance focused on supported, user-facing usage.
No functional changes are introduced. This is a documentation correctness and clarity improvement only.