Skip to content

Conversation

@handrews
Copy link
Member

@handrews handrews commented Apr 21, 2024

These formats can easily be modeled as if they were JSON arrays, with fairly minimal new tooling requirements. As documented in the linked issue, there is ample evidence for their use, and the different formats do not require different modeling approaches. This approach works for all known current streaming formats (which may or may not be literally streamed in the HTTP sense).

This seems like a nice, small-but-impactful enhancement for 3.2.0.

These formats can easily be modeled as if they were JSON arrays,
with fairly minimal new tooling requirements.
@handrews handrews added enhancement media and encoding Issues regarding media type support and how to encode data (outside of query/path params) labels Apr 21, 2024
@handrews handrews added this to the v3.2.0 milestone Apr 21, 2024
@handrews handrews requested a review from a team April 21, 2024 21:43
@handrews
Copy link
Member Author

handrews commented May 6, 2024

Moving to draft for now as 3.2 PRs that aren't ports from the patch releases can wait until after we finish the patch releases.

@handrews handrews marked this pull request as draft May 6, 2024 22:15
@handrews
Copy link
Member Author

Closing this in preparation to re-submit once the repo is re-organized for 3.2

@handrews handrews closed this Oct 19, 2024
@handrews handrews deleted the streaming-json branch June 19, 2025 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement media and encoding Issues regarding media type support and how to encode data (outside of query/path params)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants