render_turbo_stream 4.1.2 → 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 +8 -8
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 2890a165737b10c770a2ff1b8c88256d549e8798be45b4fd9670fccf34bf8b47
4
- data.tar.gz: 5592014bd80074ecdba8634092d9c40993e20e2974d04e1f35ed7a85bd9e2024
3
+ metadata.gz: 25d63c5bb45cb0783c6a9aa3c3ac8a4461d6da84d23d8e136c7b6d3183173976
4
+ data.tar.gz: 46e70462fdefc9d0eb5147dbfc411c0d1901da40de7c32207566ce5a4a3dd289
5
5
  SHA512:
6
- metadata.gz: 36d121a2321e94035616dc883c6bf040afca4aeeb7c585f3fc019ea08183104dfce115682ceb9ded56c42f5f5c902b037363ecf46bfc311efbc30c75e42aa693
7
- data.tar.gz: 4d643145ef762fd33ac6021533fc3876fbad24552fbebffffa15e6aae3efa99e635da4861261cc07248101b1e22178a83c5b2dbae21ffd5a9d867834edeb6057
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.2"
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.2
4
+ version: 4.1.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - christian
@@ -25,12 +25,12 @@ 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: For reducing the amount of System Tests that
32
- are hard to maintin, this gem allows detailled request tests! A demo project with
33
- all this built in, along with system and request tests, is linked in the README.'
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
+ system tests, this gem allows detailed request tests! A demo project with all this
33
+ built in, along with system and request tests, is linked in the README.'
34
34
  email:
35
35
  - christian@sedlmair.ch
36
36
  executables: []
@@ -86,5 +86,5 @@ requirements: []
86
86
  rubygems_version: 3.4.12
87
87
  signing_key:
88
88
  specification_version: 4
89
- summary: Complete workflow for turbo with a testing strategy.
89
+ summary: Complete workflow for turbo-rails with a testing strategy.
90
90
  test_files: []