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
spark-swagger does not handle bounded types well (see manusant/spark-swagger#14). As a result, the ResponseList type in the swagger output shows the data field as a string type. This might be resolvable by making some changes to spark-swagger (manusant/spark-swagger#15 is a work in progress) or there may be some changes made to the post-processing of the swagger output. More discussion on this was had here (reproduced in the screenshot below).
The text was updated successfully, but these errors were encountered:
Hi thanks for trying-out the library and providing feedback and contributions.
In order to propper get response for typed collections, since we are dealing with an ambiguous type, the library provides a special method for this under MethodDescriptor called withResponseAsCollection.
I´m planning some improvements but you can go with this approach
spark-swagger does not handle bounded types well (see manusant/spark-swagger#14). As a result, the
ResponseList
type in the swagger output shows thedata
field as astring
type. This might be resolvable by making some changes to spark-swagger (manusant/spark-swagger#15 is a work in progress) or there may be some changes made to the post-processing of the swagger output. More discussion on this was had here (reproduced in the screenshot below).The text was updated successfully, but these errors were encountered: