render_turbo_stream 4.1.3 → 4.1.4

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/lib/render_turbo_stream/version.rb +1 -1
  3. metadata +5 -5
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: f84574351b4a3809ae143420bc6e6a144fa548d791a69be6eebd391ca7bdbe52
4
- data.tar.gz: 264845c10d4ad2e172356d686c6527cd6064d705453a20285b62b9b132024d80
3
+ metadata.gz: 25d63c5bb45cb0783c6a9aa3c3ac8a4461d6da84d23d8e136c7b6d3183173976
4
+ data.tar.gz: 46e70462fdefc9d0eb5147dbfc411c0d1901da40de7c32207566ce5a4a3dd289
5
5
  SHA512:
6
- metadata.gz: 1c981761deae86109deeaac4fa9b11d1d183ff613a848ffd887e721f35733778c5663fd9dd250d808c0c073de0a7f2021ef9d2a65b8fbef42c7a7fc64dba39cb
7
- data.tar.gz: 70964edcb775428b89ee4e5f49038a926c65e69f49dd08dba913197fa92c64f5bb4734536eef4cd6139a4f1828382326eab3f0918b793e195d6886d47a368e1f
6
+ metadata.gz: e56656889feebe38616c4ebce6b6f52fbe64dee5c28a8522007ecb90facb86ec1061ad670010c656f4d911c36313aa89e49e7626f706ec770f168a3b40d390dd
7
+ data.tar.gz: cc0f7bbbc2fa948978386def6d2989021d7d57ad7216ac2f5aace50aaca37e22be8d8c99e05fae5c69b0c7428371ddf4232313bda10266e7e20ad72590d43619
data/lib/render_turbo_stream/version.rb CHANGED
@@ -1,3 +1,3 @@
1
1
  module RenderTurboStream
2
- VERSION = "4.1.3"
2
+ VERSION = "4.1.4"
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.1.3
4
+ version: 4.1.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - christian
@@ -25,10 +25,10 @@ dependencies:
25
25
  - !ruby/object:Gem::Version
26
26
  version: 7.0.3
27
27
  description: 'A set of helpers that allow a unified workflow for TurboStream and TurboStreams::Channel.
28
- To avoid a heavy view and logic mix inside *.turbo_stream.* templates, partials
29
- and templates can be rendered directly from the controller. There is no need to
30
- write *.turbo_stream.* templates anymore. Javascript actions can also be executed
31
- directly from the controller. TESTING: To reduce the amount of hard-to-maintain
28
+ To avoid a heavy mix of view and logic, partials and templates can be rendered directly
29
+ from the controller. There is no need to write *.turbo_stream.* templates anymore.
30
+ Logic can stay on the Ruby side, in the controller. Javascript actions can also
31
+ be executed directly from the controller. TESTING: To reduce the amount of hard-to-maintain
32
32
  system tests, this gem allows detailed request tests! A demo project with all this
33
33
  built in, along with system and request tests, is linked in the README.'
34
34
  email: