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
Oftentimes, operation method returns wrapper classes which is not really important and should be filtered in the output swagger json/yaml. The example below uses scala akka-http and it's very common to return ToResponseMarshallable in every operation. This class is only a wrapper value to serialise the object its contain.
The expected swagger output components.schemas is Employee without ToResponseMarshallable.
Executing ModelConverters.getInstance().addClassToSkip("ToResponseMarshallable") won't work since it only filters annotated type, while ToResponseMarshallable is deducted from method's type return value.
Has been analysing Reader.java, seems like the filter logic is pretty much hard coded.
The text was updated successfully, but these errors were encountered:
Oftentimes, operation method returns wrapper classes which is not really important and should be filtered in the output swagger json/yaml. The example below uses scala
akka-http
and it's very common to returnToResponseMarshallable
in every operation. This class is only a wrapper value to serialise the object its contain.The expected swagger output
components.schemas
isEmployee
withoutToResponseMarshallable
.Executing
ModelConverters.getInstance().addClassToSkip("ToResponseMarshallable")
won't work since it only filters annotated type, whileToResponseMarshallable
is deducted from method's type return value.Has been analysing Reader.java, seems like the filter logic is pretty much hard coded.
The text was updated successfully, but these errors were encountered: