Rails多输入源创建数据时，如何按来源返回带错误的视图？

Alright, let's fix this redirect issue so your validation errors show up on the correct page. The core problem right now is that your else block has two identical format.html redirects—Ruby will run the first one and ignore the second, which is why all failures land on the single input page. Here are two solid solutions to handle this:

Solution 1: Detect File Upload via Params #

Since your file upload page sends a params[:course][:file] parameter, we can use that to distinguish between the two input methods. We'll also clean up the redundant @course.save call (you're saving twice right now, which is unnecessary).

Update your create action like this:

def create
  @user = current_user
  # Check if this is a file upload request (safe nil check with &.)
  is_file_upload = params[:course]&.key?(:file)

  # Initialize the course based on input type
  if is_file_upload
    @course = Course.import(params[:course][:file])
  else
    @course = Course.new(course_params)
  end

  respond_to do |format|
    if @course.save
      format.html { redirect_to courses_path, notice: '...success!' }
      format.json { render :show, status: :created, location: courses_path }
    else
      # Redirect to the correct page based on input source
      if is_file_upload
        format.html { redirect_to file_upload_page, alert: @course.errors.full_messages.join(', ') }
      else
        format.html { redirect_to input_page, alert: @course.errors.full_messages.join(', ') }
      end
    end
  end
end

Key Notes for This Solution: #

• We use params[:course]&.key?(:file) to safely check if a file was uploaded (the &. prevents errors if params[:course] is nil).
• We join error messages into a string with join(', ') because passing an array directly to alert might display raw array syntax (like ["Error 1", "Error 2"]) instead of clean, readable text.
• Ensure your Course.import method returns a valid/invalid Course instance (not nil) when processing the file—this way, validation errors get attached to @course properly for display.

Solution 2: Use a Hidden Field to Mark Input Source #

If you want a more explicit, scalable way to track the input page (great if you add more input methods later), add a hidden field to each form.

Step 1: Add Hidden Fields to Your Forms #

In your single input page (input_page):

<%= form_with(model: @course) do |form| %>
  <!-- Your existing form fields -->
  <%= form.hidden_field :source, value: 'single_input' %>
  <%= form.submit "Submit" %>
<% end %>

In your file upload page (file_upload_page):

<%= form_with(model: @course) do |form| %>
  <!-- Your file upload field -->
  <%= form.hidden_field :source, value: 'file_upload' %>
  <%= form.submit "Upload File" %>
<% end %>

Step 2: Update the Controller to Use the Hidden Field #

def create
  @user = current_user
  input_source = params[:course][:source]

  # Initialize course based on the source
  if input_source == 'file_upload'
    @course = Course.import(params[:course][:file])
  else
    # Exclude the :source parameter from strong params to avoid mass assignment issues
    @course = Course.new(course_params.except(:source))
  end

  respond_to do |format|
    if @course.save
      format.html { redirect_to courses_path, notice: '...success!' }
      format.json { render :show, status: :created, location: courses_path }
    else
      # Redirect to the matching input page
      if input_source == 'file_upload'
        format.html { redirect_to file_upload_page, alert: @course.errors.full_messages.join(', ') }
      else
        format.html { redirect_to input_page, alert: @course.errors.full_messages.join(', ') }
      end
    end
  end
end

Key Notes for This Solution: #

• Update your course_params method to allow the :source parameter (if you're using strong params):

  def course_params
    params.require(:course).permit(:source, :your_other_fields, :file)
  end
  

• This method is more maintainable—if you add a third input page later, just add a new source value and corresponding redirect logic.

Quick Cleanup: Fix the Redundant Save #

In your original code, you called @course.save twice: once before the respond_to block, then again inside the if condition. This is unnecessary and can cause unexpected behavior (like duplicate records if the first save succeeds). Both solutions above fix this by only calling @course.save once in the condition check.

内容的提问来源于stack exchange，提问作者user3763682