render_turbo_stream 4.0.1 → 4.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: caa22ab0fcd032899bc52bb3e92bc576e26bea6bb187acbe0e00b3162e78c054
-  data.tar.gz: 7314b1bb2199fb89fc83df166c5a02749c82b291ab0210ababbf1afffedfb72a
+  metadata.gz: b7a06cc371f6543af918f87ee1d80f4c3e4c9640f10bc69b540d98ee1e5e7e20
+  data.tar.gz: 69112643c6597fc51fd669d48b467bebcf100bb690f3028775cd661b72ce1568
 SHA512:
-  metadata.gz: a99d072daf0c5cfb3955790ba17aa63ddbabdd7332ced553f06abb988ad5150329f1a787da4d03b58d34b088398d6ec64b3774fde34b429f46837e13ac11418a
-  data.tar.gz: 6d16c9a72c015961e6597847d664806871f550088b0a54f8a4e4f0c0df186844de4ca1838159fcfe8243f76de0c8ca53fa0513aa688c7e091db5d648491b4d8b
+  metadata.gz: a8790ae754ac41af06d4d375fd205eae8316c0b05551eace0c3aabe56572f7e91cd505aa40d9671d6856339468342319564bd1feea1815011cc3c097af499838
+  data.tar.gz: 671730ab4d5df1918b05bd4a768336878f9d93a3cc0c43610359dd3847f85e7fd141cb6fbf99cfe6edae934afa247fa9fbb3db3d18106a02639b2a8b64478573

data/README.md

@@ -8,7 +8,7 @@ Defining templates like `(create|update).turbo_stream.haml` is a heavy mix of lo
 
 For `:replace` actions, responses must be wrapped inside a `turbo_frame_tag` with a matching `target_id`. The gem will regex the content and wrap it by a `turbo_frame_tag` if necessary but not present. This way the matching `target_id` is only defined in one place. This check only happens on the first call after restarting the application in production and on every call if precompile assets is set to true in configs.
 
-There are many different ways to handle **redirects** since turbo. The gem brings this into a workflow.
+There are many different ways to handle **redirects** since turbo. Some details are handled here.
 
 Execute [turbo_power](https://github.com/marcoroth/turbo_power) commands such as adding a css class to an html element, can be sent directly from the controller.
 

data/app/views/render_turbo_stream.turbo_stream.erb

@@ -13,13 +13,16 @@
 
   <% else %>
     <% ctl = { partial: args[:partial], target_id: args[:target_id], action: args[:action] } %>
+
+    <% target_id = RenderTurboStream::Libs.target_to_target_id(args[:target]) %>
+
     <% info = { target_id: args[:target_id], partial: args[:partial], locals: args[:locals] } %>
 
 
 
     <% if args[:action].present? %>
       <% Rails.logger.debug("  • render-turbo-stream #{args[:action].upcase} => #{info}") %>
-      <%= turbo_stream.send args[:action].to_sym, RenderTurboStream::Libs.target_to_target_id(args[:target]) do %>
+      <%= turbo_stream.send args[:action].to_sym, target_id do %>
         <% if RenderTurboStream::CheckTemplate.new(partial: args[:partial], action: args[:action]).add_turbo_frame_tag? %>
           <%= turbo_frame_tag RenderTurboStream::Libs.target_to_target_id(args[:target]) do %>
             <%= render args[:partial], locals: args[:locals]&.symbolize_keys %>

data/lib/render_turbo_stream/check_template.rb

@@ -1,8 +1,6 @@
 module RenderTurboStream
   class CheckTemplate
 
-    AUTO_ADD_TURBO_FRAME_TAG_ON_ACTION = [:replace]
-
     def initialize(partial: nil, template: nil, available_instance_variables: nil, action: nil)
       if !partial && !template
         raise 'missing attribute partial xor template'
@@ -69,7 +67,8 @@ module RenderTurboStream
         end
       end
 
-      if stack_level == 1 && AUTO_ADD_TURBO_FRAME_TAG_ON_ACTION.include?(@action.to_sym)
+      conf = Rails.configuration.x.render_turbo_stream.auto_wrap_for_actions
+      if stack_level == 1 && conf.present? && conf.include?(@action.to_sym)
         unless _code.match(/(turbo_frame_tag|turbo-frame)/)
           @result[:add_turbo_frame_tag] = true
         end

data/lib/render_turbo_stream/controller_helpers.rb

@@ -55,7 +55,7 @@ module RenderTurboStream
         if_error_alerts,
         add_notices,
         add_alerts,
-        )
+      )
       streams += flashes[:turbo_actions]
 
       streams += libs.additional_actions(
@@ -124,7 +124,11 @@ module RenderTurboStream
         elsif pr.is_a?(Hash)
           props = pr.symbolize_keys
           r = props
-          r[:target] = RenderTurboStream::Libs.target_id_to_target(props[:target_id]) if props[:target_id].present?
+          if props[:target_id].present?
+            r[:target] = RenderTurboStream::Libs.target_id_to_target(props[:target_id])
+          else
+            r[:target] = props[:target]
+          end
           raise "Missing attribute :target in #{props}" if !props[:target].present?
           r.delete(:target_id)
           r[:action] = (props[:action].present? ? props[:action] : :replace)
@@ -150,7 +154,7 @@ module RenderTurboStream
 
     # renders a partial to turbo_stream
 
-    def stream_partial( target_id, partial: nil, action: :replace, locals: {} )
+    def stream_partial(target_id, partial: nil, action: :replace, locals: {})
       render_turbo_stream(
         [
           {

data/lib/render_turbo_stream/version.rb

@@ -1,3 +1,3 @@
 module RenderTurboStream
-  VERSION = "4.0.1"
+  VERSION = "4.0.3"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: render_turbo_stream
 version: !ruby/object:Gem::Version
-  version: 4.0.1
+  version: 4.0.3
 platform: ruby
 authors:
 - christian
@@ -24,12 +24,12 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 7.0.3
-description: Handles translated flash messages, sets status, wrapps partials in the
-  necessary frames and renders via Turbo Stream or Turbo::StreamsChannel directly
-  from the controller. No need to write *.turbo_stream.* templates. Together with
-  the turbo_power gem or custom turbo_stream actions, it can run javascript. Redirects
-  can be handled easily and in multiple ways. Through request testing helpers, this
-  allows for consistent testing strategy.
+description: 'It brings TurboStreams and TurboStreams::Channel together in a unified
+  workflow with one testing strategy. It separates logic and views: All partial handling
+  can be controlled directly from the controller. No need to write *.turbo_stream.*
+  templates. A normal partial can be sent in any way. Execution of javascript actions
+  can be done directly from the controller. Demo project with all this built in along
+  with system and request tests is available.'
 email:
 - christian@sedlmair.ch
 executables: []