Hi! 👋 Very cool gem.
It's quite possible that I'm misunderstanding the intent, so this may not be a bug. Whenever I re-visit a Turbolinks page that has a render_async on it, the render_async runs again (which is great) resulting in an empty space or placeholder loading content (which is not ideal).
The hope was for this particular sometimes slow-loading page that we could
- draw a loading spinner until the content is returned
- Turbolinks caches the page
- Upon cache restore:
- the content is restored as it was from the Turbolinks cache
- render_async calls the server
- if content is different, it's replaced, but otherwise users don't see this
This happens with render_async and render_async_cache.
I made sure to follow the documentation closely, (set the turbolinks option in an initializer, the content_for is in the <head>) but I can't seem to make this work with a fresh Rails 6.0.3.3. or 6.1rc1 app. Am I misunderstanding what should happen here or is this a bug?
Hi! 👋 Very cool gem.
It's quite possible that I'm misunderstanding the intent, so this may not be a bug. Whenever I re-visit a Turbolinks page that has a
render_asyncon it, the render_async runs again (which is great) resulting in an empty space or placeholder loading content (which is not ideal).The hope was for this particular sometimes slow-loading page that we could
This happens with
render_asyncandrender_async_cache.I made sure to follow the documentation closely, (set the turbolinks option in an initializer, the
content_foris in the<head>) but I can't seem to make this work with a fresh Rails 6.0.3.3. or 6.1rc1 app. Am I misunderstanding what should happen here or is this a bug?