Slight change to Turbo Streams' description #137
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
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.
Inspired by hotwired/turbo#580
Proposal
Modify Turbo Steams' bullet description to hopefully alleviate the false assumptions that Turbo Steams need to be delivered exclusively via WebSocket. As developers we tend to skim documentation so I'm hoping a copy change might highlight the fact that we can also leverage traditional HTTP requests and responses (as well as SSEs). The original copy certainly lists the various delivery methods but I suspect if we visually distance "Turbo Streams" and "WebSocket" a bit we may keep the reader for stopping at that point in the description, "Got it! Steams -> Sockets cool! Next"
I'm happy to make any suggested copy changes and really just wanted to provide this as a starting point