ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Unresolved behavior The current Turbo Streams implementation in Rails 7.2 silently ignores actions whose target attribute does not match an element in the client DOM. No error is thrown, and the page remains unchanged. Developers face a design decision: continue relying on this silent‑ignore semantics or implement a new configuration that raises an error or
Goal Determine whether a Turbo Drive form write was processed when the server returns a Turbo Stream that targets a DOM ID missing from the page, and whether the client can safely offer a retry without duplicating a non-idempotent POST, PUT, or DELETE. Constraints Turbo Drive submits forms via fetch, does not automatically retry, and does not attach idempote
Goal Determine whether a Turbo Streams WebSocket connection remains open or automatically reconnects when the server detects that a user’s authentication has expired or been revoked. Constraints Least‑privilege enforcement relies on server‑side middleware; the stream endpoint must reject messages from unauthenticated or unauthorized users. When a session tok
turbo