hotwired / turbo-site Goto Github PK

@DaveSanders suggested that @nwjlyons' and my solution to hotwired/turbo#138 should be documented here. I figured I'd raise an issue before I pick up a PR, because this does introduce a Stimulus code example to the Turbo docs. I'm not sure whether a solution to this problem should be built into hotwired/turbo first. There's a solution in the works for Turbo alone, but I'm not sure whether that'll definitely go ahead.

Dear All,
I have an application where chat page when generated will stay the same unless somebody type some new message.

I want turbo to not fetch that page from server (after I clicked on a link) if the page was already loaded in the Browser cache.
To reload the chat Page from server, I want to provide a special "Reload" button.
This feature will reduce traffic with my server for many use cases.

Is this possible with Turbo?
Thank you
Best regards
Emeric

Turbo expects the server to respond with a 303 status code on successful form submission, but it's not mentioned anywhere in the Turbo Reference or Handbook (https://turbo.hotwired.dev/reference/drive). Same goes for the 422 status code when you want to render a form error state.

I've invited some people to use Turbo and the status code nuances really negatively impacted their learning curve (they did not use Turbo in conjunction with Rails)

Not a bug here, just a question: any way to use hotwire/turbo wordpress? :)

This may seem very nitpicky, but isn't the fan inside the turbo logo the wrong way around, i.e. it should be mirrored.

https://github.com/hotwired/turbo-site/blob/main/images/logo.svg

The fan orientation would not be ideal as gas flows from the opening to the exit.
Either the fan should be mirrored vertically or horizontally, or the chamber with opening and exit should be mirrored vertically or horizontally.

Example

/*

• [Package Error] "@hotwired/[email protected]" could not be built.
• No build output found.
• How to fix:
• • If you believe this to be an error in Skypack, file an issue here: https://github.com/skypackjs/skypack-cdn/issues
• • If you believe this to be an issue in the package, share this URL with the package authors to help them debug & fix.
• • Use https://skypack.dev/ to find a web-friendly alternative to find another package.
    */

console.warn("[Package Error] "@hotwired/[email protected]" could not be built. ");
throw new Error("[Package Error] "@hotwired/[email protected]" could not be built. ");
export default null;

We would like to translate your Turbo handbook (EN->JA) for introducing Hotwire to Japanese rails community.
We are Everyleaf Coporation in Japan.
Our company has 15 years history, and from the first of it we are experts of Ruby and Ruby on Rails.
There are two ways to do that. Translating them in new repository under our company's GH organization' or in this repository.
Which is better for you?
We think our repository is better because currently your repository looks not ready for i18n.
Of course we will specify the origin on our page, and report to you when we publish it each time.

Thank you.

• On navigating to the main page: https://turbo.hotwire.dev/ using firefox, the following appears:
• On refreshing and reloading, nothing seems to happen.

node version v18.16.0
python3 version Python 3.8.9

You can download the latest distributable script from the GitHub releases page, then reference that in your <script> tag on your page. — https://turbo.hotwire.dev/handbook/installing (§ In Compiled Form)

I think that script is missing from the build in the released archive from the source code download at https://github.com/hotwired/turbo/releases/tag/v7.0.0-beta.1

It would be handy and more accessible to make it available without installing all the tooling (or to change the doc accordingly).

Or maybe at least provide a link to https://unpkg.com/browse/@hotwired/[email protected]/dist/ if that is the “official” way.

(See previous issue on the turbo repo and answer from @sstephenson)

Do you have any plans to update the Turbo documents to v7.2.0?

As far as I see, most updates are missing in the current document: https://github.com/hotwired/turbo/releases/tag/v7.2.0

(Well, I just hope if hotwire.dev could be powered by https://www.algolia.com/ in any chances)

Firefox version 84.0.2

https://turbo.hotwire.dev/:

Chrome and Edge are fine.

Cheers for fixing!

While looking for a way to disable turbo for form submissions (due to compatibility issues while trying to add turbo to a mature rails site), I ran across this: https://stackoverflow.com/questions/70921317/how-can-i-disable-hotwire-turbo-the-turbolinks-replacement-for-all-forms-in

which links to this merged-in feature: hotwired/turbo#419

But Turbo.setFormMode appears to be undocumented on the turbo documentation site, making it's discoverability difficult, and making it unclear whether that's an intended feature or a hidden implementation detail that may change in the future.

Can we get this documented?