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
content type mapping may not be the best approach. It maps the result schema type to the streaming type type but drops generation of the schema dto. This is the expected behavior but unwanted in this case.
A better approach is probably using a result mapping. This does not work out of the box as it currently assumes to be generic wrapper type: It generates StreamingResponseBody<JsonlGetResponse200> getJsonl(). But configuring a result mapping that does not want a generic type looks like the more logic and cleaner solution.
could be something like this, saying use a plain result type with the given type:
Activity
hauner commentedon Oct 11, 2025
hauner commentedon Oct 11, 2025
content type mapping may not be the best approach. It maps the result schema type to the streaming type type but drops generation of the schema dto. This is the expected behavior but unwanted in this case.
A better approach is probably using a result mapping. This does not work out of the box as it currently assumes to be generic wrapper type: It generates
StreamingResponseBody<JsonlGetResponse200> getJsonl(). But configuring a result mapping that does not want a generic type looks like the more logic and cleaner solution.could be something like this, saying use a plain result type with the given type:
3.2: support item schema (#314)