Ruby控制器方法中可空对象校验函数需求咨询

Hey there! Let me walk you through a clean, functional-style solution for handling nullable objects in your controller methods—exactly the kind of check-like utility you're looking for.

The goal is to create a helper that validates an object's existence, runs your desired logic only if it exists, and handles error responses gracefully if it doesn't. Here's how to implement it (I'll use Ruby/Rails syntax since you mentioned select, but you can adapt this to other languages):

# In your ApplicationController or a dedicated helper module
def check(obj, error_msg: "Required resource not found", status: :not_found)
  # If the object exists (handles nil, empty strings/arrays with `present?`), run the block
  return yield(obj) if obj.present?

  # If not, send an error response and return nil to halt further processing
  render json: { error: error_msg }, status: status
  nil
end

Single Nullable Object #

This lets you chain object retrieval, validation, and logic without messy nested if statements:

def update_user
  # Fetch the user, validate it exists, then update and return it
  updated_user = check(User.find_by(id: params[:id]), error_msg: "User not found") do |user|
    user.update(user_params)
    user.reload # Return the updated version
  end

  # Only render the user if the check passed (updated_user won't be nil here)
  render json: updated_user if updated_user
end

Multiple Dependent Objects #

For cases where you need multiple objects to exist before proceeding, you can nest the check calls for a clean flow:

def create_order
  check(Product.find_by(id: params[:product_id]), error_msg: "Product not found") do |product|
    check(Customer.find_by(id: params[:customer_id]), error_msg: "Customer not found") do |customer|
      order = Order.create!(product: product, customer: customer, total: product.price)
      render json: order, status: :created
    end
  end
end

If either the product or customer is missing, the corresponding error response is sent immediately, and the rest of the logic never runs.

You mentioned that select works great for collections because it filters out nil/empty entries automatically. This check function does the same for single objects—but with built-in error handling, so you don't have to repeat if obj.present? blocks across every controller action.

If you prefer not to add a custom helper, you can use Ruby's native then method to achieve a similar functional flow:

def delete_post
  Post.find_by(id: params[:id]).then do |post|
    if post.present?
      post.destroy
      render json: { message: "Post deleted successfully" }
    else
      render json: { error: "Post not found" }, status: :not_found
    end
  end
end

This is more verbose than the custom check function, but it avoids adding new helper methods if that's a priority.

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