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
Describe the bug
I tried running the SwaggerGenerator from the 4.0.0 release and, unfortunately, it produces invalid Swagger. OpenApiGenerator has the same issue.
To Reproduce
Execute OpenApiGenerator and validate the result.
Expected behavior
Search parameters should only be listed once per type.
Additional context
There was a late change leading up to 4.0.0 in which I introduced a second entry in the search parameters map for each search parameter. In the past we only needed to look up the applicable search parameters by "code" but for Composite search we needed to look them up by "url" as well.
Obviously, I didn't know that would cause this knock-on effect to the Swagger/OpenAPI.
The text was updated successfully, but these errors were encountered:
Previously, the parameter maps built by ParametersUtil had each
SearchParameter listed twice...once by "code" and once by "url".
This pull request introduces a new ParametersMap object that
encapsulates two separate maps and presents it as a single object.
Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
Previously, the parameter maps built by ParametersUtil had each
SearchParameter listed twice...once by "code" and once by "url".
This pull request introduces a new ParametersMap object that
encapsulates two separate maps and presents it as a single object.
Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
Describe the bug
I tried running the SwaggerGenerator from the 4.0.0 release and, unfortunately, it produces invalid Swagger. OpenApiGenerator has the same issue.
To Reproduce
Execute OpenApiGenerator and validate the result.
Expected behavior
Search parameters should only be listed once per type.
Additional context
There was a late change leading up to 4.0.0 in which I introduced a second entry in the search parameters map for each search parameter. In the past we only needed to look up the applicable search parameters by "code" but for Composite search we needed to look them up by "url" as well.
Obviously, I didn't know that would cause this knock-on effect to the Swagger/OpenAPI.
The text was updated successfully, but these errors were encountered: