-
-
Notifications
You must be signed in to change notification settings - Fork 26
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: allow assigning provider-enabled instances to FastifyInstance
#43
fix: allow assigning provider-enabled instances to FastifyInstance
#43
Conversation
FastifyInstance
FastifyInstance
@RafaelGSS Hi, just noticed this PR was still pending. I think it should be ok to merge this one through as the type specs were updated on fastify/fastify#4371 in preparation for this. The original PR provided adequate testing when infering
So just as a quick reminder on this. This update relates specifically to enabling contravariance of the FastifyInstance when configured with a Type Provider. This should help greatly improve type composability and assignment of FastifyInstance (as it makes the configured provider instance assignable to non configured instances, which is awesome) I don't anticipate this change causing any problems in existing codebases currently using this or the json-schema provider. But may want to use a minor revision just in case. Would be a great to see this PR merged through! |
@driimus can you rebase? |
@RafaelGSS the PR is already up-to-date with If it's about the failing CI for node14/windows, that shouldn't be related to the changes in this PR. It sounds more like tapjs/tapjs#843. The project doesn't have a lockfile so the version of tap that gets installed is newer than the one in
I've created a clone of the repo to run the CI workflow on
Unless the tap issue (or npm/cli#5856) is resolved quickly, there might be a need to coordinate the fix across repos in the fastify org. |
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 think the most appropriate is to release the minor when the tap issue is resolved. |
Checklist
npm run test
andnpm run benchmark
and the Code of conduct
Fix for fastify/fastify#4342 specific to this type provider.