You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Maybe/ But actually $ref support were added some time before to fastify-oas, so there's a change that it will work.
I'm planning to create new branch for 3.x stuff testing. If you want to experiment as well - PRs always appreciated.
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can go ahead and create the 3.x branch and change the fastify version requirement to include v3?
My API schemas currently don't use the $ref but this module throws an error about the required fastify version even though it works on v3 (without $ref usage).
That way we can simply add "fastify-oas": "SkeLLLa/fastify-oas#3.x" to our package.json in the meanwhile.
fbfccc1
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.
@SkeLLLa any info if it will work for new fastify v3?
fbfccc1
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.
It should, but we'll need some testing. So we just need some tests.
fbfccc1
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.
probably the new schema ref stuff will not work: https://github.com/fastify/fastify/blob/master/docs/Migration-Guide-V3.md#changed-schema-substitution-2023
fbfccc1
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.
Maybe/ But actually $ref support were added some time before to fastify-oas, so there's a change that it will work.
I'm planning to create new branch for 3.x stuff testing. If you want to experiment as well - PRs always appreciated.
fbfccc1
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.
have done a first quick test: #30
fbfccc1
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.
Maybe we can go ahead and create the
3.x
branch and change the fastify version requirement to includev3
?My API schemas currently don't use the
$ref
but this module throws an error about the required fastify version even though it works onv3
(without$ref
usage).That way we can simply add
"fastify-oas": "SkeLLLa/fastify-oas#3.x"
to ourpackage.json
in the meanwhile.fbfccc1
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.
@MichielDeMey give me couple of hours and I create branches and publish
@next
tag to npm.fbfccc1
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.
@MichielDeMey
https://github.com/SkeLLLa/fastify-oas/tree/next
https://www.npmjs.com/package/fastify-oas/v/3.0.0-rc.0