Fix middleware order: Move Logger before Recoverer #6
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 addresses an issue with the order of middleware in the router setup. According to the chi documentation, the Logger middleware should be placed before any other middleware that may change the response, such as Recoverer middleware. In the current implementation, the Logger middleware is placed after the Recoverer middleware, which may result in incorrect logging behavior.
Changes made:
By making this change, the middleware order will now be in compliance with chi's recommendations, ensuring proper logging behavior.