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
Hey guardrail is a super great project and I love it but I'm here to report a bug:
Generating clients for akka-http. Using the maven plugin 0.59.0.
In my spec file I choose a x-jvm-type nested inside some request paramters on a Post. The generated client ends up taking String instead of the type I specified.
Just some further info so I don't forget, because I got confused about this:
This does work for array properties in an object specified in components/schemas (or definitions for Swagger v2).
This does not work for array parameters specified on a request.
This does not work for array properties in an object specified in-line in a requestBody.
Ultimately we want to unify these things so we don't need this code in three places; they are separate because the Swagger v2 used different model representations, but the OAPI v3 parser does actually model these things the same way.
Hey guardrail is a super great project and I love it but I'm here to report a bug:
Generating clients for akka-http. Using the maven plugin 0.59.0.
In my spec file I choose a
x-jvm-type
nested inside some request paramters on a Post. The generated client ends up takingString
instead of the type I specified.Example snippet:
The generated client has this:
I expected the two
Iterable[String]
to beVector[ServerlessFileVersionSid]
Have attempted a workaround of moving the
#!
lines above to a$ref
but generated client didn't change.The text was updated successfully, but these errors were encountered: