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
In http4s there is streamJsonArrayEncoderOf which allows you to use fs2.Stream but encode it as a valid JSON Array.
When in one of our services we switched to Tapir for endpoints definitions, we noticed that this functionality is missing, or at the very least we are not sure how to achieve it.
For us, this is very useful, as for short streams, it allows for easier integration with different tools that might not understand NDJSON or other approaches.
As a workaround we roll out our own stream json array encoding, but It'd be nice to have this built-in in Tapir, maybe as an opt-in.
The text was updated successfully, but these errors were encountered:
This is definitely doable (a matter or providing a way of translating a Stream[F, MyCaseClass] to Stream[F, Byte]), though it would need to reside in a fresh module depending on: circe, fs2 and tapir. A bit specialised ... but maybe worth it?
Hello!
In http4s there is streamJsonArrayEncoderOf which allows you to use fs2.Stream but encode it as a valid JSON Array.
When in one of our services we switched to Tapir for endpoints definitions, we noticed that this functionality is missing, or at the very least we are not sure how to achieve it.
For us, this is very useful, as for short streams, it allows for easier integration with different tools that might not understand NDJSON or other approaches.
As a workaround we roll out our own stream json array encoding, but It'd be nice to have this built-in in Tapir, maybe as an opt-in.
The text was updated successfully, but these errors were encountered: