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
fix: multiple route same schema #2108
Conversation
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
I can confirm that this patch fixes issue with fastify-oas plugin, so LGTM. |
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
Can it be published? |
I'll prep a release asap. |
I think it had been already published in 2.12.1 v2.12.1...master |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Fixes #2104
Related #2044
This PR revert the #2044 fix and implement it in a different way but the same test cannot pass because when the user adopts the
querystring
alias (akaquery
) we modified the original object adding thequerystring
parameter.The previous test was a
deepEquals
check with the original objectNow it is a
deepEquals
with the original object plus thequerystring
field.So I think this PR is more in line with the older versions of fastify compared to v2.12
This is a "nice" edge case.. I will keep it in mind for the future during the reviews 😅
Checklist
npm run test
andnpm run benchmark