Rewrite v7 exceptions page for problem details - #170
Merged
Conversation
The extend walkthrough named paths, a trait and a helper that no longer exist; documents the ten real exceptions and the ::create() factory. Signed-off-by: arhimede <julian@dotkernel.com>
alexmerlin
approved these changes
Sep 8, 2026
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
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.
The "How to extend" walkthrough taught a model the application no longer has: create a plain Exception, then add a catch block to HandlerTrait::handle() returning $this->errorResponse(). That directory, trait and helper do not exist, and neither do MethodNotAllowedException or OutOfBoundsException.
Every exception now implements ProblemDetailsExceptionInterface and sets its own status inside a static create() factory, so extending is one new class and nothing else. The walkthrough builds a TeapotException and shows the 418 document it produces.
Also documents the ten real exceptions with the status each one sets and what raises it, the four create() arguments and their fallbacks, the two paths ProblemDetailsMiddleware takes, and the fact that 404 and 405 come from router middleware rather than application exceptions.
Verified against dotkernel/api at 7.0, commit 45ad282.
Fixes C6 of the v7 documentation audit.