render_turbo_stream 0.1.34 → 0.1.36

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 95e94563d2f1c54311f3755286e2ace6f4f258c63f443b305043cf2c7611cd4f
-  data.tar.gz: e7deed853515642b52503f1f870e436ad4870359320b7fc88d179e10b9d60943
+  metadata.gz: 2c7532451ee9d808af49593c554e304f1f4de4f82f561378bf449ae7e9933722
+  data.tar.gz: c967685bd9bb8476536af267ad2e9fe24b66ef5ca63ba48b6aef6501621c6cf4
 SHA512:
-  metadata.gz: a34007581d53530c7f96f1aff79af28594303c856dea1913708d913794a4020f8203c98ffd8a6538446e1a85295436a7d466ff1e09f3171615af7eac6afff781
-  data.tar.gz: f7fa39fbd0932a58112168abe638f323f1f3a3ae98d1ddd9fc700e504d741dfbc04dfb666ecd34cff42ff6b6ca0ab236ad94fbd05e48f55c8b75b5da19593c10
+  metadata.gz: 293fdcc0dff25264324482dd433a31507756b73526edc0ab31786e9b08a9e4a86e18cc82b932065b0ff329cded36439cdee2944dbc99440c77359714615f8f73
+  data.tar.gz: edde20365f6a575f4dafde9166100b4e3ff4d54cd72ac0f4e767d9b67fb798e7923fe0b906b0f8d3976227f035bcc70cf9d51d1cc408581048083cdaa2219366

data/README.md

@@ -2,11 +2,15 @@
 
 Defining templates like `(create|update).turbo_stream.haml` annoyed me.
 
-Working consistently with turbo_stream means shooting lots of partials from the backend to the frontend, which always needs the same attributes: ID, partial, and maybe some locals. This gem serializes that: Partials can be controlled directly from the controller.
+Working consistently with turbo_stream means shooting lots of partials from the backend to the frontend, which always
+needs the same attributes: ID, partial, and maybe some locals. This gem serializes that: Partials can be controlled
+directly from the controller.
 
-It sets the status, generates a flash message, handles redirection, pushes it all to the front and comes with predefined helpers for enabling request-specs.
+It sets the status, generates a flash message, handles redirection, pushes it all to the front and comes with predefined
+helpers for enabling request-specs.
 
-An overview of how we design a rails-7 application with turbo is [published on dev.to](https://dev.to/chmich/rails-7-vite-wrapping-up-1pia).
+An overview of how we design a rails-7 application with turbo
+is [published on dev.to](https://dev.to/chmich/rails-7-vite-wrapping-up-1pia).
 
 ## Installation
 
@@ -34,35 +38,39 @@ end
 
 Redirection
 
-For redirection to work, you must follow the installation steps from [turbo_power](https://github.com/marcoroth/turbo_power).
+For redirection to work, you must follow the installation steps
+from [turbo_power](https://github.com/marcoroth/turbo_power).
 
 Required Configurations for Flash Partial
 
 ```ruby
     config.x.render_turbo_stream.flash_partial = 'layouts/flash'
-    config.x.render_turbo_stream.flash_id = 'flash-box'
-    config.x.render_turbo_stream.flash_action = 'prepend'
+config.x.render_turbo_stream.flash_id = 'flash-box'
+config.x.render_turbo_stream.flash_action = 'prepend'
 ```
 
 The corresponding partials for flashes could look [like this](https://gitlab.com/sedl/renderturbostream/-/wikis/flashes)
 
 ## Usage
 
-`turbo_stream_save` is a special method for streamlining `update` or `create` functions for `turbo_stream`, which might look like this:
+`turbo_stream_save` is a special method for streamlining `update` or `create` functions for `turbo_stream`, which might
+look like this:
 
 ```ruby
- def create
-    @customer = Customer.new(customer_params)
 
-    turbo_stream_save(
-      @customer.save,
-      redirect_on_success_to: edit_customer_path(@customer)
-    )
+def create
+  @customer = Customer.new(customer_params)
 
-  end
+  turbo_stream_save(
+    @customer.save,
+    redirect_on_success_to: edit_customer_path(@customer)
+  )
+
+end
 ```
 
-This will set a status, generate a flash message and perform `stream_partials`, which could result in something like this:
+This will set a status, generate a flash message and perform `stream_partials`, which could result in something like
+this:
 
 ```ruby
 stream_partials(
@@ -93,35 +101,40 @@ stream_partial(
 
 ## Testing
 
-For system testing we have Capybara. This works great and is necessary for javascript and backend combined apps, but it is good practice to break tests into smaller pieces. 
+For system testing we have Capybara. This works great and is necessary for javascript and backend combined apps, but it
+is good practice to break tests into smaller pieces.
 
 For the much faster request-level tests, there are some helpers:
 
-If the request format is not `turbo_stream`, which is the case on request specs, the method responds in a special html that contains the medadata that is interesting for our tests and is parsed by included test helpers. So tests could look like this:
+If the request format is not `turbo_stream`, which is the case on request specs, the method responds in a special html
+that contains the medadata that is interesting for our tests and is parsed by included test helpers. So tests could look
+like this:
 
 ```ruby
 require 'rails_helper'
 include RenderTurboStream::TestHelpers
 
 RSpec.describe "Articles", type: :request do
-  
+
   let(:invalid_params) { { article: { title: '', desciption: 'abc' } } }
 
   it 'create failed' do
-    
+
     post articles_path(params: invalid_params)
 
-    # --- BASIC TEST ---
-    
-    # Count of rendered partials
-    expect(partials_count).to eq(2)
-    # Make sure that each of these partials is rendered exactly once.
-    expect(partials_once).to include('layouts/flash', 'articles/form')
-    
-    
-    
-    
-    # --- MORE OPTIONS ---
+    # ----- BASIC -----
+
+    # Which partials were rendered
+    expect(partials).to include('layouts/flash', 'articles/form')
+
+    # Exactly Which partials were rendered to which ids
+    expect(
+      partials_once(
+        { partial: 'layouts/flash', id: 'flash-box' },
+        { partial: 'articles/form', id: 'form' })
+    ).to be_truthy
+
+    # ----- MORE OPTIONS -----
 
     # to which html-ids turbo-stream would point
     expect(partials_ids).to include('flash-box', 'form')
@@ -143,7 +156,7 @@ RSpec.describe "Articles", type: :request do
     expect(partials_responses(id: 'flash-box').length).to eq(1)
 
     # Same with partials
-    
+
     expect(partials_responses(partial: 'layouts/flash').length).to eq(1)
   end
 end
@@ -161,7 +174,8 @@ end
 
 P.S.:
 
-Testing the plugin itself: There is a [quick-and-dirty app](https://gitlab.com/sedl/renderturbostream_railsapp) which includes the plugin and has tests done by rspec/request and capybara.
+Testing the plugin itself: There is a [quick-and-dirty app](https://gitlab.com/sedl/renderturbostream_railsapp) which
+includes the plugin and has tests done by rspec/request and capybara.
 
 ## Parameters for turbo_stream_save
 
@@ -212,4 +226,5 @@ example value: `"%<model_name>s successfully created"`
 Contribution welcome.
 
 ## License
+
 The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).

data/lib/render_turbo_stream/version.rb

@@ -1,3 +1,3 @@
 module RenderTurboStream
-  VERSION = "0.1.34"
+  VERSION = "0.1.36"
 end

data/lib/render_turbo_stream.rb

@@ -97,6 +97,7 @@ module RenderTurboStream
     flash_partial = Rails.configuration.x.render_turbo_stream.flash_partial
     flash_action = Rails.configuration.x.render_turbo_stream.flash_action
     flash_notices.each do |notice|
+      next unless notice.present?
       # inside the flash partial has to be a loop that handles all theese flashes
       flash_stream = {
         id: flash_id,
@@ -107,6 +108,7 @@ module RenderTurboStream
       streams.push(flash_stream)
     end
     flash_alerts.each do |alert|
+      next unless alert.present?
       # inside the flash partial has to be a loop that handles all theese flashes
       flash_stream = {
         id: flash_id,

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: render_turbo_stream
 version: !ruby/object:Gem::Version
-  version: 0.1.34
+  version: 0.1.36
 platform: ruby
 authors:
 - christian