Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete coverage of Hotwire capabilities (other than Streams) #5

Open
jvissers opened this issue Sep 29, 2021 · 0 comments
Open

Complete coverage of Hotwire capabilities (other than Streams) #5

jvissers opened this issue Sep 29, 2021 · 0 comments

Comments

@jvissers
Copy link
Contributor

I'm doubting whether this is an issue or just something that needs clearing up (in respective README.md).

Hotwire consists of a number of things:

  1. Turbo Drive accelerates links and form submissions by negating the need for full page reloads.
  2. Turbo Frames decompose pages into independent contexts, which scope navigation and can be lazily loaded.
  3. Turbo Streams deliver page changes over WebSocket, SSE or in response to form submissions using just HTML and a set of CRUD-like actions.

Seems like the project only deals with Turbo Streams. Is that the case? If yes, would it be possible to add an example(s) for Drive and Frames (much like what DHH is showing in the Hotwire demo). If no, can you maybe update the README.md to point to the code/example that deals with those other functionalities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant