plutonium 0.60.5 → 0.62.0

data/lib/plutonium/resource/controller.rb

@@ -14,7 +14,9 @@ module Plutonium
       include Plutonium::Resource::Controllers::Presentable
       include Plutonium::Resource::Controllers::Queryable
       include Plutonium::Resource::Controllers::CrudActions
+      include Plutonium::Resource::Controllers::KanbanActions
       include Plutonium::Resource::Controllers::InteractiveActions
+      include Plutonium::Resource::Controllers::WizardActions
       include Plutonium::Resource::Controllers::Typeahead
       include Plutonium::Resource::Controllers::ExportCsv
       include Plutonium::StructuredInputs::ParamsConcern
@@ -161,13 +163,34 @@ module Plutonium
             extraction_record.respond_to?("#{k}=") &&
               extraction_record.class.reflect_on_association(k.to_sym).nil?
           }
-          extraction_record.assign_attributes(submitted.slice(*(base_keys | extra_keys)))
+          # Never assign attachment/file inputs to the throwaway extraction_record:
+          # the submitted value is a single-read Rack upload (UploadedFile), and a
+          # Shrine attacher consumes it to EOF on assign — so the later
+          # `resource_class.new(resource_params)` would re-read a closed stream
+          # ("IOError: closed stream"). Active Storage escaped this because its
+          # attachment reflects as an association (excluded above); Shrine's virtual
+          # `file=` accessor does not, so exclude file inputs explicitly. The value
+          # still reaches create/update via `extract_input` (which reads params, not
+          # this record), so nothing is dropped — the file is just read once, later.
+          assign_keys = (base_keys | extra_keys) - attachment_input_keys
+          extraction_record.assign_attributes(submitted.slice(*assign_keys))
           extracted = build_form(extraction_record, form_action: false)
             .extract_input(params, view_context:)[resource_param_key.to_sym].compact
           clean_structured_inputs(current_definition, extracted)
         end
       end
 
+      # Attachment/file input names (as Strings) declared on the current
+      # definition — inputs whose `as:` is a file type (`:file`/`:uppy`/
+      # `:attachment`). Excluded from the extraction-record pre-assignment so a
+      # single-read Rack upload isn't consumed before create/update reads it.
+      def attachment_input_keys
+        file_types = Plutonium::UI::Form::Base::Builder::FILE_INPUT_TYPES
+        current_definition.defined_inputs.filter_map { |name, config|
+          name.to_s if file_types.include?(config.dig(:options, :as)&.to_sym)
+        }
+      end
+
       # Returns the resource parameters, including scoped and parent parameters
       # @return [Hash] The resource parameters
       def resource_params

data/lib/plutonium/resource/controllers/crud_actions.rb

@@ -56,6 +56,7 @@ module Plutonium
               format.turbo_stream { render turbo_stream: turbo_stream.replace(helpers.turbo_scoped_dom_id("resource-form"), view_context.render(build_form(action: :new))) }
               format.html { render :new, status: :unprocessable_content }
             elsif resource_record!.save
+              after_create_persisted
               format.turbo_stream do
                 flash.notice = "#{resource_class.model_name.human} was successfully created."
                 render turbo_stream: stacked_modal_create_streams
@@ -142,7 +143,7 @@ module Plutonium
                 notice: "#{resource_class.model_name.human} was successfully deleted."
             end
             format.json { head :no_content }
-          rescue ActiveRecord::InvalidForeignKey
+          rescue ActiveRecord::InvalidForeignKey, ActiveRecord::DeleteRestrictionError
             format.turbo_stream do
               flash.alert = "#{resource_class.model_name.human} is referenced by other records."
               render turbo_stream: helpers.turbo_stream_redirect(resource_url_for(resource_record!))
@@ -164,6 +165,13 @@ module Plutonium
 
         private
 
+        # Hook fired once, immediately after a successful create-save and BEFORE
+        # the response is built. No-op by default. KanbanActions overrides it to
+        # apply a kanban quick-add column's on_enter + positioning to the freshly
+        # created (already-persisted) record; the reload/redirect response is built
+        # after this returns, so the board reflects the placement.
+        def after_create_persisted = nil
+
         # When the create came in through the secondary (stacked) modal
         # frame — i.e. the user clicked "+" next to an association field
         # while the parent form was already in a modal — we don't want to