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
Hi
I'm trying to develop a component which exposes its own API as defined in the swagger model, but for a couple of endpoints has to call an external service, and expose directly the results from it, acting as a sort of proxy.
Is it that possible using the api-first-hand plugin?
I mean: I expected to be able to use a definition similar to the following one:
But it will produce a case class ItemsGetResponses200() "empty" (no fields).
Using AnyValue, object or {}object schema, I always get the same behaviour.
Is there maybe a default model I could use here?
I'm fine declaring models first, but for this case only I really can't: I have to put the data in the response as they were from the external service, and still declare at least the endpoint and its parameters for swagger.
Does anybody has any idea on how to accomplish that? tanks in advance
Alfredo
The text was updated successfully, but these errors were encountered:
Hi
I'm trying to develop a component which exposes its own API as defined in the swagger model, but for a couple of endpoints has to call an external service, and expose directly the results from it, acting as a sort of proxy.
Is it that possible using the api-first-hand plugin?
I mean: I expected to be able to use a definition similar to the following one:
But it will produce a
case class ItemsGetResponses200()
"empty" (no fields).Using
AnyValue
,object
or{}
object schema, I always get the same behaviour.Is there maybe a default model I could use here?
I'm fine declaring models first, but for this case only I really can't: I have to put the data in the response as they were from the external service, and still declare at least the endpoint and its parameters for swagger.
Does anybody has any idea on how to accomplish that? tanks in advance
Alfredo
The text was updated successfully, but these errors were encountered: