-
-
Notifications
You must be signed in to change notification settings - Fork 80
Fix / route with prefix in fastify@v3.10.1 #98
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
Conversation
@@ -113,6 +110,6 @@ function close (fastify, done) { | ||
} | ||
|
||
module.exports = fp(fastifyWebsocket, { | ||
fastify: '3.x', | ||
fastify: '>= 3.10.1', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does not qualify as a breaking change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, in a real world application you should use lock files, so this wouldn't impact you until you want to upgrade.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If removing this line really fixes it - then why was that line necessary before? Was the double onRoute
a bug in Fastify?
Because otherwise, that‘d be a breaking change in 3.10 (a Minor) that‘s mentioned nowhere in the release notes.
This was caused by: https://github.com/fastify/fastify/pull/2782/files. We had a few bugs in other plugins because it was called twice. (Note that the change in Fastify was not causing any tests failures here). cc @salmanm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
We should add a similar test in Fastify core.
@Skn0tt double |
Fix #97
Checklist
npm run test
andnpm run benchmark
and the Code of conduct