Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(guides): breaking change exposeHeadRoutes #4047

Merged
merged 2 commits into from Jun 19, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/Guides/Migration-Guide-V4.md
Expand Up @@ -27,6 +27,12 @@ In some situations, like when a response is sent asynchronously or when you're
just not explicitly returning a response, you'll need to return the `reply`
argument from your router handler.

### `exposeHeadRoutes` true by default

Starting from v4, all the `GET` routes will create a sibling `HEAD` route.
You can revert this behaviour by setting the server's option `exposeHeadRoutes`
to `false`.

## Non Breaking Changes

### Change of schema for multiple types
Expand Down