1

在asp.net mvc中，actiondispatcher会在action中将params变成模型，这个过程称为模型绑定，在rails中怎么称呼？rails 3中的质量分配，rails 4中的强参数？

如果我的表单有很多输入字段，格式为100,000.00，当我提交表单时，我需要保留所有值的格式然后验证表单，如何在模型中格式化以用于保险目的？</p>

更新：

 # find all numeric attributes and define a write_attribute method
 all_numeric_columns = Deal.columns.select {|x| [:float, :integer, :decimal].include?(x.type)}.map(&:name)
 all_numeric_columns.each do |column|
   class_eval <<-METHOD, __FILE__, __LINE__ + 1
     def #{column}=(the_value)
      write_attribute(:#{column}, the_value.gsub(',', ''))
     end
   METHOD
 end
4

1 回答 1

0

批量分配是正确的。params[:your_models_name]您可以通过传递给YourModel.new或来创建或更新模型YourModel.find(params[:id]).update_attributes params[:your_model]。强参数是一种将可以批量分配的参数列入白名单的方法。

从指南：

class PeopleController < ActionController::Base
  # Using "Person.create(params[:person])" would raise an
  # ActiveModel::ForbiddenAttributes exception because it'd
  # be using mass assignment without an explicit permit step.
  # This is the recommended form:
  def create
    Person.create(person_params)
  end

  # This will pass with flying colors as long as there's a person key in the
  # parameters, otherwise it'll raise an ActionController::MissingParameter
  # exception, which will get caught by ActionController::Base and turned
  # into a 400 Bad Request reply.
  def update
    redirect_to current_account.people.find(params[:id]).tap { |person|
      person.update!(person_params)
    }
  end

  private
    # Using a private method to encapsulate the permissible parameters is
    # just a good pattern since you'll be able to reuse the same permit
    # list between create and update. Also, you can specialize this method
    # with per-user checking of permissible attributes.
    def person_params
      params.require(:person).permit(:name, :age)
    end
end

在上面的示例中，如果传入的参数如下所示：

{ 
  person: {
    name: 'bob',
    age: 30,
    admin: true
  } 
}

那么这个admin: true参数就不会被分配给 bob 的 Person。

至于您的输入字段格式问题，它们应该出现在表单上。这不适合你吗？

于 2013-11-13T07:00:19.897 回答