render_turbo_stream 4.0.4 → 4.0.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: b5298cf405518f297f86cdd2581e39d618e3f750046335d425d5187035352380
4
- data.tar.gz: 2cd649610255db9ca104884a472521f19af864f3f4f14eae5a2f55628f8b94ea
3
+ metadata.gz: 35bd786f43a61b85aa26d790277b3e912687f4831abc9abcc677e936e5b978f2
4
+ data.tar.gz: 511c55b6ad3e503d76bb5f2aefa1f9d85fbffed996bc7e304e94944b78a75fcd
5
5
  SHA512:
6
- metadata.gz: 6a26003bfecef2adfd2b5cf263b06ce0106601e4c9893d25d3ab28d004ed7422324107c3d2f318047bb8b5b52a69e8887a36399a8bcec02761292480042b9eeb
7
- data.tar.gz: 79810dadb98ec80ba893744767c7000b14f7bb98652c052d9ccfe8ee807ba17fc87045015c451521223aaebd51f924deef49e18546a6c04e11d143edaf2a3c36
6
+ metadata.gz: 5955c95a112371c9bd890d03ce16288ab484c3bccd5c36b74d532cfc1e73993426c6f1d61f9665e7ff474ae45b760478c2c15f90bce82d7ccfcf590e4f248a74
7
+ data.tar.gz: 829ffda44d7e230c314cec9b29d1617833983fdba23a1422bde8e5c28f0bfde7fb098733fa6ef85f06bfc41605e4afab8028eefe930a231f620fa504602e837f
data/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  2021 DHH annouced a great milestone in web development with [Rails 7, "Fulfilling a Vision"](https://rubyonrails.org/2021/12/15/Rails-7-fulfilling-a-vision).
4
4
 
5
- To say it up front: If you want to have all the benefits of Turbo without disturbing the handy default Rails workflow, you must use WebSockets sometimes, which are well integrated in Turbo, see [README Turbo::StreamsChannel](https://gitlab.com/sedl/renderturbostream/-/blob/main/README-channels.md). But the starting point is here. And I recommend that you download my [Quick-and-dirty test project](https://gitlab.com/sedl/renderturbostream_railsapp), set it up, see all the tests succeed, and then read through this README.
5
+ This gem has a second [README Turbo::StreamsChannel](https://gitlab.com/sedl/renderturbostream/-/blob/main/README-channels.md). Starting point is here. And I recommend that you download my [Quick-and-dirty test project](https://gitlab.com/sedl/renderturbostream_railsapp), set it up, see all the tests succeed, and then read through this README.
6
6
 
7
7
  Defining templates like `(create|update).turbo_stream.haml` is a heavy mix of logic and view. This gem separates logic and view so that `*.turbo_stream.*` templates are no longer necessary and the logic can stay on the ruby side.
8
8
 
@@ -151,6 +151,9 @@ module RenderTurboStream
151
151
  if a.is_a?(Hash) && a.key?(:target_id)
152
152
  a = a.merge(target: "##{a[:target_id]}")
153
153
  a.delete(:target_id)
154
+ unless a.key?(:action)
155
+ a[:action] = :replace
156
+ end
154
157
  a
155
158
  else
156
159
  a
@@ -1,3 +1,3 @@
1
1
  module RenderTurboStream
2
- VERSION = "4.0.4"
2
+ VERSION = "4.0.5"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: render_turbo_stream
3
3
  version: !ruby/object:Gem::Version
4
- version: 4.0.4
4
+ version: 4.0.5
5
5
  platform: ruby
6
6
  authors:
7
7
  - christian
@@ -24,12 +24,12 @@ dependencies:
24
24
  - - ">="
25
25
  - !ruby/object:Gem::Version
26
26
  version: 7.0.3
27
- description: 'It brings TurboStreams and TurboStreams::Channel together in a unified
28
- workflow with one testing strategy. It separates logic and views: All partial handling
29
- can be controlled directly from the controller. No need to write *.turbo_stream.*
30
- templates. A normal partial can be sent in any way. Execution of javascript actions
31
- can be done directly from the controller. Demo project with all this built in along
32
- with system and request tests is available.'
27
+ description: This gem brings a set of helpers that allow a unified workflow for TurboStream
28
+ and TurboStreams::Channel and allow a complete and detailed testing strategy. To
29
+ avoid a heavy view and logic mix inside *.turbo_stream.* templates, this allows
30
+ to completely separate view and logic and control all templates and partials directly
31
+ from the controller. Javascript actions can also be executed directly from the controller.
32
+ A demo project with all this built in along with system and request tests is available.
33
33
  email:
34
34
  - christian@sedlmair.ch
35
35
  executables: []