Using turbostreams with wicked? about wicked HOT 1 OPEN

Ultimately, I think I was able to work around my specific issue

Clicking this link will change the value of some_variable via turbostreams:

step_b.html.erb:

<%= turbo_frame_tag "foo_frame" do %>
  <%= some_variable %>
<%= end %>

<%= link_to "step b", step_b_path(some_variable: "new value of some_variable"), data: { "turbo_stream": true } %>

Somewhere inside your view for step_b you'll need a link with data-turbo-stream=true. This will cause the link click to be of type "text/vnd.turbo-stream.html", which is a typical turbo-stream request. Then when we later do respond_to do |format| that will tell rails to execute the format.turbo_stream code in your steps controller.

steps_controller.rb

def show
    respond_to do |format|
      case step
      when :step_a
        # dostuff
        
      when :step_b
        if request.referrer.include? wizard_url
          format.turbo_stream { render turbo_stream: turbo_stream.update("foo_frame", partial: path_to_partial, locals: { some_variable: params[:some_variable] }) }
        end
        
      when :step_c
        # dostuff
      
      format.html { render_wizard }
    end
end

I'm not 100% certain, but it seems that when navigating from step_a to step_b it's trying to process it as a turbostream and doesn't render the view for step_b. It may be because I have a nested turbostream in my case. However, I wanted to be able to target and replace a specific, nested turbostream.

The line if request.referrer.include? wizard_url basically just says "If the request is coming from the same step_b page, then perform this turbostream update on the "foo" turboframe. Therefore this code won't execute when transitioning from step_a to step_b, which resolves the issue described above. However, this doesn't seem like an ideal solution

from wicked.