Lets say I have map like this fetching from my database %{"_id" => #BSON.ObjectId<58eb1a7a9ad169198c3dXXXX>, "email" => "XXXX@gmail.com", "name" => "Hariharasudhan", "password_hash" => "XXXX", "phone" => "XXXX"} and i have struct like follow > @primary_key{:id, :binary_id, autogene…

I use this code. lib/mappable.ex master def to_map(nil) do nil end @default_options [ keys: :atoms, shallow: false, skip_unknown_atoms: false, warn_unknown_atom…

@manukall If i try struct(%User{}, %{"_id" => #BSON.ObjectId<58eb1a7a9ad169198c3dXXXX>, "email" => "XXXX@gmail.com", "name" => "Hariharasudhan", "password_hash" => "XXXX", "phone" => "XXXX"} ) am getting output like %User{meta: #Ecto.Schema.Metadata<:built, “users”>, countryCode: nil, email: n…

Keys from the map must be atoms, as only atoms are allowed in struct definition.

@matteosister yes, but map returned from db has string keys, Is there is any way to conevrt??

Wow, I’m pretty surprised that this isn’t built in, or at least available as part of Phoenix since incoming json data is not exactly an unexpected occurence in that context. Sure, it’s simple to manually add, and I understand the point about using strings instead of atoms for external data. Still, f…

Poison let’s you do this ergonomically: Poison.decode!(~s({"name": "Devin Torres", "age": 27}), as: %Person{})

Many thanks! :folded_hands:t2: I knew I was missing something.

Ah, as it turns out that won’t work for my purposes. I’m not trying to grab the values from a literal and when if I use inspect to get a string dump of the map, it’s obviously not going to come out as proper JSON. Ah well. I’ll write a clever macro at some point, I reckon.

Untested, but it seems like cast and apply_changes should do what you want: %User{} |> Ecto.Changeset.cast(map, User.__schema__(:fields)) |> Ecto.Changeset.apply_changes()