Rails Devise强参数无法构建嵌套关联问题排查

已生成Devise控制器和视图，定义了User与Account模型如下：

User模型 #

class User < ApplicationRecord
  # Include default devise modules. Others available are:
  # :confirmable, :lockable, :timeoutable, :trackable and :omniauthable
  devise :database_authenticatable, :registerable,
         :recoverable, :rememberable, :validatable,
         :confirmable, :lockable, :timeoutable, :trackable,
         :omniauthable, omniauth_providers: [ :google_oauth2 ]

  has_one :account, autosave: true, dependent: :destroy, inverse_of: :user

  before_validation :set_account
  enum :role, { basic: 0, admin: 1, courier: 2, client: 3 }

  def set_account
    self.build_account
  end
  accepts_nested_attributes_for :account
end

Account模型 #

class Account < ApplicationRecord
  belongs_to :user, autosave: true
end

强参数配置 #

class Users::RegistrationsController < Devise::RegistrationsController
  before_action :configure_signup_parameters, only: :create
.
.
.
 protected

  # If you have extra params to permit, append them to the sanitizer.
  def configure_signup_parameters
    added_attrs = [ :first_name,
                    :last_name,
                    :name,
                    :email,
                    :password,
                    :password_confirmation,
                    :card_name,
                    :card_number,
                    :card_cvv,
                    :card_expiration_month,
                    :card_expiration_year,
                    account_attributes: [
                      :name,
                      :plan,
                      :plan_discount_pct,
                      :plan_period,
                      :plan_price,
                      :tier
                    ]
    ]
    devise_parameter_sanitizer.permit(:sign_up, keys: added_attrs)
  end
end

日志显示嵌套属性数据已传入，但Rails创建Account时所有值为空：

Processing by Users::RegistrationsController#create as HTML
  Parameters: {"authenticity_token"=>"[FILTERED]", "user"=>**{"account_attributes"=>{"tier"=>"corporate", "plan"=>"SMB", "name"=>"Batman", "plan_period"=>"GoldAnnual"}**, "first_name"=>"Bruce", "last_name"=>"Wayne", "name"=>"Batman", "email"=>"[FILTERED]", "password"=>"[FILTERED]", "password_confirmation"=>"[FILTERED]"}, "card_name"=>"Bruce Wayne", "card_number"=>"[FILTERED]", "card_expiration_month"=>"[FILTERED]", "card_expiration_year"=>"[FILTERED]", "card_cvv"=>"[FILTERED]", "save"=>"1", "commit"=>"Submit"}
  TRANSACTION (0.2ms)  BEGIN /*action='create',application='Freighteen',controller='registrations'*/
  User Exists? (6.5ms)  SELECT 1 AS one FROM "users" WHERE "users"."email" = 'batman@dc.com' LIMIT 1 /*action='create',application='Freighteen',controller='registrations'*/
  CACHE User Exists? (0.0ms)  SELECT 1 AS one FROM "users" WHERE "users"."email" = 'batman@dc.com' LIMIT 1
  User Create (0.5ms)  INSERT INTO "users" ("email", "encrypted_password", "reset_password_token", "reset_password_sent_at", "remember_created_at", "sign_in_count", "current_sign_in_at", "last_sign_in_at", "current_sign_in_ip", "last_sign_in_ip", "confirmation_token", "confirmed_at", "confirmation_sent_at", "unconfirmed_email", "failed_attempts", "unlock_token", "locked_at", "created_at", "updated_at", "name", "first_name", "last_name", "role") 

VALUES ('batman@dc.com', '$2a$12$MoG2NgRuikEE9yEMguK4iOybH7MN3BmDRS6sf78SUNJpK.rx9z3Cu', NULL, NULL, NULL, 0, NULL, NULL, NULL, NULL, 'sGBMeBMesDm-2h3j9Jcj', NULL, '2025-01-05 04:41:22.332196', NULL, 0, NULL, NULL, '2025-01-05 04:41:22.331966', '2025-01-05 04:41:22.331966', 'Batman', 'Bruce', 'Wayne', 0) RETURNING "id" /*action='create',application='Freighteen',controller='registrations'*/
  **Account Create (0.6ms)  INSERT INTO "accounts" ("user_id", "created_at", "updated_at", "tier", "plan", "plan_period", "plan_discount_pct", "plan_price", "name") VALUES (11, '2025-01-05 04:41:22.341682', '2025-01-05 04:41:22.341682', NULL, NULL, NULL, NULL, 0.0, NULL) RETURNING "id"**

注意account属性已存在但未被正确保存，当前配置无需手动构建，请问遗漏了什么？

问题出在before_validation :set_account回调上——它会在参数赋值之后重新构建一个空的Account实例，直接覆盖掉通过嵌套属性传入的Account数据。

修复步骤：

1. 移除before_validation :set_account回调和对应的set_account方法，accepts_nested_attributes_for已经能处理关联对象的创建，且你已经在请求参数中传入了account_attributes，无需额外手动构建。
2. 如果需要确保User实例始终关联Account，可以改用after_initialize回调，同时避免覆盖已存在的关联：

class User < ApplicationRecord
  # ... 其他代码 ...
  has_one :account, autosave: true, dependent: :destroy, inverse_of: :user
  accepts_nested_attributes_for :account

  after_initialize do
    build_account unless account.present?
  end
  # ... 其他代码 ...
end

3. 额外检查Account模型的数据库字段约束：如果字段设置了NOT NULL但请求中未传入对应值（比如日志里没传的plan_discount_pct和plan_price），Rails会自动设为NULL或默认值，但这不是当前问题的核心原因，修复回调后即可解决属性为空的问题。

修复完成后，日志中的Account Create语句应该会包含传入的tier、plan、name、plan_period等值。

内容的提问来源于stack exchange，提问作者Michael K Madison