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
openapi: 3.0.0
info:
title: Test API
description: test spec
version: 0.0.1
paths:
/test/v1/endpoint:
get:
parameters:
- $ref: https://dev-apiforge.cvshealth.com/api-oas/global-domains/test-domain-v1~0.0.1.yaml#/components/parameters/A
- $ref: http://localhost:3000/oas/test-domain-v1~0.0.1.yaml#/components/parameters/B
responses:
'200':
description: Success.
content:
application/json:
schema:
$ref: http://localhost:3000/oas/test-domain-v1~0.0.1.yaml#/components/parameters/A
Describe the bug you're encountering
I have refs retrieved through an API endpoint. They are properly returned and resolved inside the editor. However, swagger-ui has a problem resolving them.
When expanding an operation an error displays:
Resolver error at paths./test/v1/endpoint.get.parameters.0.$ref
Could not resolve reference: Could not resolve pointer: /components/parameters/A does not exist in document
Screenshots
Expected behavior
Additional context or thoughts
Interestingly, when added the reference files to the public folder and referencing them through there, there is no error. However it is undesirable to require a new build every time a ref is modified or added to the referenced file.
The text was updated successfully, but these errors were encountered:
Content & configuration
Describe the bug you're encountering
I have refs retrieved through an API endpoint. They are properly returned and resolved inside the editor. However, swagger-ui has a problem resolving them.
When expanding an operation an error displays:
Screenshots
Expected behavior
Additional context or thoughts
Interestingly, when added the reference files to the public folder and referencing them through there, there is no error. However it is undesirable to require a new build every time a ref is modified or added to the referenced file.
The text was updated successfully, but these errors were encountered: