feat: allow newline runs in data #2786
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
https://html.spec.whatwg.org/multipage/server-sent-events.html#event-stream-interpretation |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR allows runs of
\nchars to be included in an event stream data. Subsequently this will stop\nfrom being stripped from a message and includes it in the payload.This is helpful in a use case where the server needs to send text with multiple lines in a single event.
I believe this still aligns with the SSE specification since I cannot find specifics around removing/including newline runs. Please let me know what you think of this change and if anything should be updated.
Thanks