fix(resolve schema reference): shortcut if definitions is undefined#830
Draft
jpb06 wants to merge 1 commit intofastify:mainfrom
Draft
fix(resolve schema reference): shortcut if definitions is undefined#830jpb06 wants to merge 1 commit intofastify:mainfrom
jpb06 wants to merge 1 commit intofastify:mainfrom
Conversation
|
Hi ! I missed this PR but I openned yesterday an issue on fastify-zop-openapi for the exact same problem samchungy/fastify-zod-openapi#172 I explained the problem with a repo that reproduce the bug https://github.com/mottet/bug-fastify-zod-openapi I have the same conclusion about the fix in lib/util/resolve-schema-reference.js |
Author
|
Thanks @mottet ! |
4 tasks
|
Ah. Just spotted this. Submitted #836 yesterday which is related |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello. Firstof, thanks for maintaining this lib 🙇🏻
It appears this fix is causing an issue with our codebase. We have an endpoints that is is defined like this:
which resolves to a schema like this:
{ "components": { "schemas": { "MyResponse": { "type": "object", "properties": { // ... } } } }, "paths": { "/my-endpoint": { "get": { "responses": { "200": { "description": "Default Response", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/MyResponse", } } } } } } } } }The issue is there is no definitions for this ref, which makes the whole thing crash. Wasn't the case before.
One simple fix is to check if
resolvedReference.definitionsisundefinedbefore trying to access it.I tried to write a test to reproduce the issue but I'm not an openapi expert so I can't seem to get anywhere:
This fails with:
Any help would be appreciated. Thank you!
Checklist
npm run testandnpm run benchmarkand the Code of conduct