More from Henry Kim

RSS

A reusable respond_to block for turbo_stream + html

2687 views

0 comments

                  module TurboResponder
  extend ActiveSupport::Concern

  def respond_turbo_or_html(success_redirect:, invalid_template:)
    respond_to do |format|
      format.turbo_stream
      format.html { redirect_to success_redirect, status: :see_other }
    end
  rescue ActionController::UnknownFormat
    render invalid_template, status: :unprocessable_entity
  end
end

                  class ProjectsController < ApplicationController
  include TurboResponder

  def create
    @project = Project.new(project_params)
    return render(:new, status: :unprocessable_entity) unless @project.save

    respond_turbo_or_html(success_redirect: @project, invalid_template: :new)
  end
end

Once you’ve built a few Hotwire controllers, you notice the same respond_to shape repeated. I extract a small helper (a concern) that yields a respond_to block and centralizes the “default HTML redirect” pattern. This keeps controllers readable and reduces subtle inconsistencies (like returning 200 instead of 422 on invalid). The trick is not to hide too much—controllers still decide which template to render—but you can standardize status codes and fallbacks. I also like to use this to enforce status: :see_other for redirects. It’s a small refactor that pays back quickly as the app grows.

Henry Kim

More from Henry Kim

A reusable respond_to block for turbo_stream + html

0 Comments

More from Henry Kim