bullet_train 1.6.3 → 1.6.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c76cb66088988d0ed0e9e1b2f444f4377bd8ba8531d2ec6f9d00b7374e8d5f0f
-  data.tar.gz: 29dfa7afdad1612cb2ac44b264d408877dea791e34f670f34b2b2cc0c73b5384
+  metadata.gz: 0f600ed43bf526b425a8401848ec54cb2560cb7fa0e45fe2e0b6a2976949e975
+  data.tar.gz: d0833d3c1ce80839f416fec71d4b38a2099942cc3cd01e5e2712fbb2f4cf0501
 SHA512:
-  metadata.gz: 5b2e8240126515b5b6abf0015efa63ac4c320173c4c97508843627487434aaa87a04fe5cf2a691c8e7059cd6458334ab201911b7384ddb86e3abee01df680755
-  data.tar.gz: 23e1a5035a6b5c0d8d52af7ab529ecd9b7fbae774e34fb6655c3f72056f17d16492b1bfa2ede9e270280fa516bb8b7e11fd20931a29ef8ff081f3f103fa6eabb
+  metadata.gz: 77246baefaeb8fce78e10c6202410b5952589edbc6391777ed3b671db4b3e89b622684273c49440cac103b159b733a1cd5b08445a57fc95e6a9f86722d5d106a
+  data.tar.gz: c98756ba46b9d2349d687a79e28930cc8aba287dc65d4cedc093bc4a21bf3ebea5f160dd8b2df296a55a6d1dc081ebe1da4340cc850b6fbe8f93e6ea31660241

data/docs/field-partials/super-select.md

@@ -71,6 +71,32 @@ Here is an example allowing a new option to be entered by the user:
 </code></pre>
 
 Note: this will set the option `value` (which will be submitted to the server) to the entered text.
+
+To handle the new entry's text on the server, use `ensure_backing_models_on`.
+
+`ensure_backing_models_on` validates an `id:` or multiple `ids:` against a passed Active Record relation, and yields for each missing id so you can create backing models. Like this:
+
+```rb
+if strong_params[:category_id]
+  strong_params[:category_id] = ensure_backing_models_on(current_team.categories, id: strong_params[:category_id]) do |scope, id|
+    scope.find_or_create_by(name: id)
+  end
+end
+```
+
+In case our form had `multiple: true`, we could have used `ids:` instead:
+
+```rb
+if strong_params[:category_ids]
+  strong_params[:category_ids] = ensure_backing_models_on(current_team.categories, ids: strong_params[:category_ids]) do |scope, id|
+    scope.find_or_create_by(name: id)
+  end
+end
+```
+
+Note, if you need to constrain the collection further you could pass any extra scope, e.g. `current_team.categories.not_archived`.
+
+
 ## Events
 
 All events dispatched from the `super_select` partial are [Select2's jQuery events][select2_events] re-dispatched as native DOM events with the following caveats:
@@ -115,11 +141,11 @@ import { Controller } from "stimulus"
 
 export default class extends Controller {
   static targets = [ "dependentField" ]
-  
+
   updateDependentFields(event) {
     const originalSelect2Event = event.detail.event
     console.log(`catching event ${event.type}`, originalSelect2Event)
-    
+
     this.dependentFieldTargets.forEach((dependentField) => {
       // update dependentField based on value found in originalSelect2Event.target.value
     })
@@ -152,4 +178,4 @@ If you'd like to:
 * modify other fields based on the value of your `super_select`, or
 * modify your `super_select` based on the value of other fields
 
-See [Dynamic Forms and Dependent Fields](/docs/field-partials/dynamic-forms-dependent-fields.md).
+See [Dynamic Forms and Dependent Fields](/docs/field-partials/dynamic-forms-dependent-fields.md).

data/lib/bullet_train/version.rb

@@ -1,3 +1,3 @@
 module BulletTrain
-  VERSION = "1.6.3"
+  VERSION = "1.6.4"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bullet_train
 version: !ruby/object:Gem::Version
-  version: 1.6.3
+  version: 1.6.4
 platform: ruby
 authors:
 - Andrew Culver
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-10-13 00:00:00.000000000 Z
+date: 2023-10-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: standard