Upgrade to latest version of kin-openapi #957
Labels
Comments
jamietanna
added a commit
that referenced
this issue
Aug 23, 2023
As noted in #936, we have an issue where a number of circular references may be expected and allowed, so we should provide the ability to configure this, allowing users to decide what makes sense for them. This requires we add an additional method, `LoadSwaggerWithCircularReferenceCount`, as the existing method is part of our public API and we cannot modify it without breaking consumers. This is already available in the version of kin-openapi we're using, we're just configuring it. Closes #936, #957.
jamietanna
added a commit
that referenced
this issue
Aug 23, 2023
As noted in #936, we have an issue where a number of circular references may be expected and allowed, so we should provide the ability to configure this, allowing users to decide what makes sense for them. This requires we add an additional method, `LoadSwaggerWithCircularReferenceCount`, as the existing method is part of our public API and we cannot modify it without breaking consumers. This is already available in the version of kin-openapi we're using, we're just configuring it. Closes #936, #957.
jamietanna
added a commit
that referenced
this issue
Aug 23, 2023
As noted in #936, we have an issue where a number of circular references may be expected and allowed, so we should provide the ability to configure this, allowing users to decide what makes sense for them. This requires we add an additional method, `LoadSwaggerWithCircularReferenceCount`, as the existing method is part of our public API and we cannot modify it without breaking consumers. This is already available in the version of kin-openapi we're using, we're just configuring it. Closes #936, #957.
jamietanna
added a commit
that referenced
this issue
Aug 23, 2023
As noted in #936, we have an issue where a number of circular references may be expected and allowed, so we should provide the ability to configure this, allowing users to decide what makes sense for them. This requires we add an additional method, `LoadSwaggerWithCircularReferenceCount`, as the existing method is part of our public API and we cannot modify it without breaking consumers. This is already available in the version of kin-openapi we're using, we're just configuring it. Closes #936, #957.
debuggerpk
pushed a commit
to breuHQ/oapi-codegen
that referenced
this issue
Sep 18, 2023
As noted in deepmap#936, we have an issue where a number of circular references may be expected and allowed, so we should provide the ability to configure this, allowing users to decide what makes sense for them. This requires we add an additional method, `LoadSwaggerWithCircularReferenceCount`, as the existing method is part of our public API and we cannot modify it without breaking consumers. This is already available in the version of kin-openapi we're using, we're just configuring it. Closes deepmap#936, deepmap#957.
|
Apologies for not closing this at the time, we've since done this a few times! |
jamietanna
added
dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The latest version is v0.114.0 as of the time of writing. oapi-codegen v1.12.4 is still using kin-openapi v0.107.0 but I'm seeing that
masteris already using v0.112.0 so that looks promising.This might resolve #936.
Background: getkin/kin-openapi#764.
Thank you!
The text was updated successfully, but these errors were encountered: