Skip to content
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

Server routes with more than one `consumes` duplicates parameters (2to3 shims bug) #324

blast-hardcheese opened this issue Jun 9, 2019 · 0 comments


None yet
1 participant
Copy link

commented Jun 9, 2019

In Swagger specifications, there was no differentiation between the different content types for HTTP bodies submitted to any given endpoint.

As a result, when converting swagger to OpenAPI 3.x, it's necessary to duplicate all parameters for each content type in the resulting specification.

Unfortunately, it seems as though parameters are concatted irrespective of mediaType without deduplicating them.

This results in:

[error] .../PetClient.scala:45:98: name is already defined as value name
[error]   def updatePetWithForm(petId: Long, name: Option[String] = None, status: Option[String] = None, name: Option[String] = None, status: Option[String] = None, headers: List[HttpHeader] = Nil): EitherT[Future, Either[Throwable, HttpResponse], UpdatePetWithFormResponse] = {
[error]                                                                                                  ^
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.