turbo_stream.remove not removing entity about turbo-rails

[dhh]

Yeah, going to come up with a way to fix this. Right now you do need that empty response. You can also do { render turbo_stream: "" }. But it's ugly as well. We'll find a better way.

[j-sieg]

I think you can get it to work if you remove the stimulus controller and just use
<%= button_to 'Delete', user_path(user), method: :delete %>

[dhh]

By doing a remote link that's triggering a fetch outside of Turbo, you're not going to be sending an Accept header that includes turbo stream. So you'll be hitting either the html or json formats. What @j-sieg said is the way to go. It's better for a11y to use real forms for actions anyway.

[bborn]

Is a head :ok the right thing for the server to respond with here? If so, would it make sense for turbo-rails to provide a default? Otherwise, if you do this:

def destroy
  def destroy
    @message = Message.find(params[:id])
    @message.destroy

    respond_to do |format|
      format.turbo_stream 
    end
  end

Then you have to provide a blank destroy.turbo_stream.erb to avoid getting a missing template error.