fields.nested_form[:update_only] should always be false by default.

[antoine-lizee]

See the "first bug" in this stack overflow answer.

It's a personal opinion, but I think that interpreting accept_nested_attributes_for: ..., update_only:true as "disable the form when creating the object" is a potential misunderstanding of the option, (for Rails 4), and should at least be documented in the wiki?

[ericcf]

@antoine-lizee as a first step, I've created a gist to reproduce the issue here: https://gist.github.com/ericcf/f4da02ca5bb80d889131f603448ee10c

There is a difference between update_only: true and update_only: false, which seems like a bug to me as well based on the description in the Rails documentation. In my example, accepts_nested_attributes_for :dog, update_only: false leads to being able to add a Dog record upon creation of a Person, which seems to be correct.

@sferik is this interpretation correct? Would you like a failing spec for this case or is more discussion necessary? Thanks.

[GProst]

We're having the same issues because of the misunderstanding of this option by Rails Admin. It's unexpected that you can't create a new association for a model when update_only is set to true for accept_nested_attributes_for

[myers]

BTW, if you do the following:

RailsAdmin.config do |config|
  config.model 'User' do
    base do
      configure :location do
        nested_form[:update_only] = false
      end
    end
  end
end

In order to get Rails Admin to show the child form when creating a instance, you will actually change the settings on the model as nested_form returns the same hash used to configure the model.

You should do this instead:

      configure :location do
        nested_form(nested_form.clone)
        nested_form[:update_only] = false
      end