-
Notifications
You must be signed in to change notification settings - Fork 208
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
OpenAPI 3.0: $ref path string that includes a dot (name.name) doesn't import correctly. #36
Comments
Hi, First of all i would like to thank JP-from-Postman for filing this issue. Your sincerely, Raymond Asbreuk |
Hi, Any updates on the above? Could you give any estimate on when this ticket is going to be picked up/fixed? Your sincerely, Raymond Asbreuk |
Hi, Do you have any updates on the questions i asked above. Gr, Raymond Asbreuk |
@rasbreuknedap Thanks for the detailed report, and apologies for the delay here. I've opened up a PR for this fix - #54. We can make a release for this module soon, but this will only be updated in the next version of the Postman app. You can use this as a stand-alone module till then. |
@rasbreuknedap The fix has been included in Postman 7.1.0. |
Hi, just noticed that references that include dots cannot be clicked to "go to reference". A fix would be awesome, thanks!!! |
ISSUE
When importing an OpenAPI 3.0 .json file, with a $ref that points to a component path, if the path string contains a
.
(example:"$ref": "#/components/schemas/item.otherItem"
), the path isn't resolved correctly, and shows an error like the following in the field where the $ref was used:"value": "reference #/components/schemas/item.otherItem not found in the api spec"
Replacing the
.
s with a_
, allows the file to import correctly.REPRODUCE:
.
s used)openapi3_works_not.json.zip
No response was specfied
for the request:com.nedap.healthcare.api.benchmark.Benchmark API.client Migration
For comparison, try importing following file (where
.
s are replaced with_
)openapi3_works.json.zip
The text was updated successfully, but these errors were encountered: