inputs_for should iterate over the related models contents if no changes were given about phoenix_ecto HOT 9 CLOSED

I don't follow this one.

José Valim
www.plataformatec.com.br
Skype: jv.ptec
Founder and Director of R&D

from phoenix_ecto.

@josevalim now if I want to show currently present items I have manually convert them to params and call cast. E.g.:

nested = build_nested_params(model.nested)
changeset = Model.changeset(changeset, %{"nested" => nested})

If I don't do this I get an empty form.

Which is quite as written in the source here and here

from phoenix_ecto.

Can you tell me if it would work if you build it as:

changeset = Model.changeset(changeset, :empty)

I am almost sure it is required to build a changeset. The :empty parameters does it for you.

from phoenix_ecto.

It does if I put a model instead of changeset as a first parameter. But in my particular case, a controller's action already have params, so it becomes Model.changeset(Model.changeset(model), params) which is not very intuitive and should be documented at least.

from phoenix_ecto.

@sumerman I see and I agree. I will try to find a solution.

from phoenix_ecto.

@josevalim thanks for this and for all your work.

from phoenix_ecto.

Ok, this is more complicated than expected because, for embeds, the data is always there... which means defaults would never be triggered.

When are you first generating the changeset? Are you generating it with the :empty parameter?

from phoenix_ecto.

First time it's generated by another controller action, then it's shown as a form to a user who modifies it then it shown as an immutable part of the form which becomes a param-only initialization of the changeset. And yes, initially it's generated with :empty parameter. Also there is a problem with Model.changeset(Model.changeset(model), params) but I will open a separate issue on elixir-lang/ecto for it.

from phoenix_ecto.

Fixed in master. We now always take the value in the model into account.

from phoenix_ecto.