Where are you inspecting that? After calling Ash.Changeset.change_attributes/2?
zachdaniel
Creator of Ash
dewetblomerus
@zachdaniel thanks for hanging in there with this long thread! Your question just made me find something really interesting.
I was not inspecting it, I was just looking at the return value in Livebook.
When I inspect the Ash.Changeset after calling Ash.Changeset.change_attributes/2, it is valid?: true
The only code where I am doing something wrong is where I am calling it form LiveBook.
changeset =
user
|> Ash.Changeset.for_update(
:register_with_auth0,
%{
user_info: user_info,
oauth_tokens: %{}
}
)
That is when I get the error about no email, but if I inspect inside the action, right after calling change_attributes/2, it says there are no errors.
I tried to change it to Ash.Changeset.for_create but then I get the following error:
** (ArgumentError) Initial must be a changeset with the action type of `:create`, or a resource.
Got: #Red.Accounts.User<
What confuses me about this error, is that it says it must be a changeset or a resource, my understanding is that it is a resource.
0
zachdaniel
Creator of Ash
dewetblomerus
GOT IT! Thank you!
This works perfectly from Livebook, which is what we were trying to get to with the last ~7 messages
Red.Accounts.User
|> Ash.Changeset.for_action(
:register_with_auth0,
%{
user_info: user_info,
oauth_tokens: %{}
}
)
|> Red.Accounts.create!()
And it does change updated_at every time it is called, even if nothing changed.
0
dewetblomerus
zachdaniel
Creator of Ash
I don’t recall what I was getting at 
But I think what I was implying was try to call the action in iex (with the upsert_fields: {:replace_all_except, ...} option passed that was giving you trouble) as opposed to submitting a form.
1
dewetblomerus
Oh right! Here it is.
** (Ash.Error.Unknown) Unknown Error
* ** (Protocol.UndefinedError) protocol Enumerable not implemented for {:replace_all_except, [:updated_at]} of type Tuple. This protocol is implemented for the following type(s): DBConnection.PrepareStream, DBConnection.Stream, Date.Range, Ecto.Adapters.SQL.Stream, File.Stream, Function, GenEvent.Stream, HashDict, HashSet, IO.Stream, Jason.OrderedObject, List, Map, MapSet, Phoenix.LiveView.LiveStream, Postgrex.Stream, Range, Stream, StreamData
(ash 2.17.0) lib/ash/api/api.ex:2324: Ash.Api.unwrap_or_raise!/3
/Users/dewet/code/ash/red/README.livemd#cell:7cjnls2owec2pmsah6gswm3qjxo6sxou:43: (file)
0
zachdaniel
Creator of Ash
Looks like a regular old bug on that one. I think we haven’t added the logic for transforming the new formats for upsert_fields when it’s provided as an option. Could you open an issue on Ash?
0
dewetblomerus
Thanks a million for all the effort you have put into something that was merely an annoyance for me. The least I can do is open an issue. I’ll also try to provide a more minimal example for reproducing it. I don’t think Ash Authentication or Phoenix would need to be involved.
1