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
We’ve implemented a new handler (for streaming responses) by providing instances of HasServer, HasClient, Accept, and HasSwagger. This works reasonably well, but now we've run into an issue where the type-level machinery used by validateEveryToJSON (i.e. BodyTypes) can’t be extended in a similar way, and in fact it silently ignores endpoints that use the new type. I don’t know if this approach can be made to handle this, but it would be an improvement if it at least gave an error saying that it can’t discover all the types.
We’ve implemented a new handler (for streaming responses) by providing instances of
HasServer
,HasClient
,Accept
, andHasSwagger
. This works reasonably well, but now we've run into an issue where the type-level machinery used byvalidateEveryToJSON
(i.e.BodyTypes
) can’t be extended in a similar way, and in fact it silently ignores endpoints that use the new type. I don’t know if this approach can be made to handle this, but it would be an improvement if it at least gave an error saying that it can’t discover all the types.The problem is the “default” case on this line:
servant-swagger/src/Servant/Swagger/Internal/TypeLevel/API.hs
Line 81 in 735657b
The text was updated successfully, but these errors were encountered: