render_turbo_stream 4.0.1 → 4.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: caa22ab0fcd032899bc52bb3e92bc576e26bea6bb187acbe0e00b3162e78c054
-  data.tar.gz: 7314b1bb2199fb89fc83df166c5a02749c82b291ab0210ababbf1afffedfb72a
+  metadata.gz: 35750e37d2f65c71588b62ebcd0b7986d0e0012bd8674808dd0149f81b5ee967
+  data.tar.gz: 3937766529f3c5418b29895196c5a8acbb1bfeecf0e6464faf7c310d1a5ac097
 SHA512:
-  metadata.gz: a99d072daf0c5cfb3955790ba17aa63ddbabdd7332ced553f06abb988ad5150329f1a787da4d03b58d34b088398d6ec64b3774fde34b429f46837e13ac11418a
-  data.tar.gz: 6d16c9a72c015961e6597847d664806871f550088b0a54f8a4e4f0c0df186844de4ca1838159fcfe8243f76de0c8ca53fa0513aa688c7e091db5d648491b4d8b
+  metadata.gz: c0cd96285c1d01d203b5afd33094f4be26606c40e70bab2161a36202219f713f273ae97534dc35bf722b5fe7091e034b68028c0f2f9513e20b3346d45c3f1b67
+  data.tar.gz: ebdbca94432c7e14d01e93729e8d9361d5ffacba0ea90b20148d22882e2e7bd248dda610d8a840db6cfecdddffbe94eaa139f7527e432079fc8231525a709541

data/README.md

@@ -8,7 +8,9 @@ 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.
+If the turbo stream action is `:replace' and the content is not wrapped by `turbo_frame_tag', the gem will wrap it. So the partial content is checked by regex. 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. 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/lib/render_turbo_stream/version.rb

@@ -1,3 +1,3 @@
 module RenderTurboStream
-  VERSION = "4.0.1"
+  VERSION = "4.0.2"
 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.2
 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: []