A detail guide of Controller callbacks.

[danschultzer]

A detail guide of Controller callbacks.

[danschultzer]

Looks good to me, and it'll be easy to refactor!

A note is that if the :userinfo association is preloaded on the user, it'll update instead of replacing it with changeset (the docs describe how it works).

Also, instead of checking id, you can just check if the struct is persisted: Ecto.get_meta(user, :state) != :loaded.

[danschultzer]

You can do this modifying the changeset method adding the user info as a nested changeset like so:

def changeset(user_or_changeset, attrs) do
  user
  |> pow_changeset(attrs)
  |> pow_extension_changeset(attrs)
  |> cast_assoc(:user_info, required: true)
end

This will call the changeset method in your UserInfo schema module.

I think this is the most appropriate way. I'll probably leave ControllerCallbacks out of readme as it's mostly for well-versed developers. The issue you experience is because it'll only pull the extension callbacks. You'll have to create a different controller callback module. But it'll be a lengthy explanation, and I think the nested association would work here.

[danschultzer]

Oh, the hex docs on cast_assoc/3: https://hexdocs.pm/ecto/Ecto.Changeset.html#cast_assoc/3

[jung-hunsoo]

Oh great. Thanks. You're right that Changeset is the best place. It's ironic that I migrated from Coh.. to Pow because redirect doesn't work. (#372 there) If I utilized cast_assoc/3 there I still reside there.

Anyway I finally managed to make it work as expected. Not a pretty codes though:

  def changeset(user, attrs) do
    attrs = refine_attrs(user, attrs)

    user
    |> pow_changeset(attrs)
    |> pow_extension_changeset(attrs)
    |> Ecto.Changeset.cast(attrs, [:nickname, :locale, :role])
    |> Ecto.Changeset.validate_required([:nickname])
    |> Ecto.Changeset.unique_constraint(:nickname)
    |> Ecto.Changeset.cast_assoc(:userinfo, required: true)
  end

  @doc false
  defp refine_attrs(user, attrs) do
    if !Map.get(user, :id) && map_size(attrs) > 0 do
      case Map.keys(attrs) |> hd |> is_atom do
        true  -> Map.put(attrs, :userinfo, %{})
        false -> Map.put(attrs, "userinfo", %{})
      end
    else
      attrs
    end
  end

:userinfo is added when a new user is created, so that even from default Pow operations can be worked too.

I already was aware of cast_assoc/3, but didn't know this can work. UUID was my walkaround for this situation, and other libs too. Like note in Arc.

I've learned one good thing haha. Thanks. Now my webapp is working smoothly.