-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[SPIKE] Resolve $ref
in api/controller/route specs
#435
Comments
This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the |
|
I am keeping this in CoreGA scope, I'd like to know the estimate before deciding whether to keep or push out this feature. |
$ref
in api/controller/route specs$ref
in api/controller/route specs
This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
At the moment, our code processing Swagger/OpenAPI Spec does not support
$ref
references, we assume all entities have been denormalized/dereferenced. IMO, this is a severe limitation because even the simples CRUD-based REST APIs usually reuse model (response object) definitions.We should investigate how to support
$ref
in all places allowed by OpenAPI spec. Let's limit the scope to relative references only (e.g.#/definitions/User
) and exclude external references (e.g.http://json-schema.org/address
).Acceptance Criteria
The text was updated successfully, but these errors were encountered: