orangy
GsonSupport
was mainly coded as a POC for bidirectional pipelines. Honestly we shouldn’t have released it, don’t use it. It has too many limitations and issues like the one you described. Best thing for now is using manually encoded JSONs, like adding a respondJson
extension function and using it instead of relying on that installed feature. I’m working on a proper ContentNegotiation
feature, with customisable encoder selector and proper responses like Not Acceptable
for strict mode, and selecting some “default” encoder if proper negotiation didn’t occur.