Maybe you could be the change you want to see in the world 
zachdaniel
Creator of Ash
melissaloh
Curious about what writing the book has been like? 
Rebecca Le’s talk Writing the book on Ash from our recent Elixir Sydney meetup is now available.
You can watch it over here:
6
vkryukov
Hello everyone,
I finally found time to read the “Ash Framework” book, and now finishing Chapter 5. The book is very clearly written, and carefully explains a lot of important concepts - thanks @sevenseacat and @zachdaniel !
I have a quick question about the “confirm your email address” email that is automatically sent as part of the password verification strategy. It doesn’t seem that the verification status is saved anywhere (no relevant field in User resource, for example) - is that something that the users of AshAuthentication are supposed to add themselves?
1
vkryukov
And I just noticed that the migration does create a confirmed_at field, which is probably what is updated by the AshAuthentication code, it’s just not exposed as an attribute to the user. What’s the rationale for this decision?
0
zachdaniel
Creator of Ash
When you say not exposed to the user, do you mean why is it not marked as a public attribute? You’re free to mark it as public if you want.
0
vkryukov
What I meant is that confirmed_at is not present in the User’s attributes section, which looks like this:
attributes do
uuid_primary_key :id
attribute :email, :ci_string do
allow_nil? false
public? true
end
attribute :hashed_password, :string do
sensitive? true
end
end
Now, while it’s not mentioned in the book, the attribute is mentioned in the documentation, and I can see it been part of the migration that was automatically generated. I understand that I can simply add it to the attribute section myself; I was just curious why it was not defined there in the first place? Is that because it is only relevant for some authentication strategies but not others? Or is it considered for internal use only, and the developer is not supposed to access it directly but through some helper method?
0
zachdaniel
Creator of Ash
Ah, right. So I actually think that is an oversight. You can add the attribute to that list. The way that AshAuthentication works is a mix of modifying the resource (like under the hood) and verifying the resource. When we made the switch to focus on generating more information into the end-user’s application, we probably just missed the confirmed_at attribute. Could you open an issue for us to add that to the installer?
If you do Ash.Resource.Info.attribute(YourResource, :confirmed_at) you will see that it actually does have that resource. Extensions have the ability to add and remove all kinds of things in that way. If you added the confirmed_at attribute, the extension wouldn’t add it but would use yours instead.
2
AndyL
Just read the first chapter - the book is great. I spent time studying Ash a couple years ago. Things have come a long way. The igniter generators are a giant improvement. My favorite Ash change: renaming “API” to “Domain”. I asked Grok3 what it knows about Ash: seems like quite a lot, and Grok seems informed about recent releases. (it reads the hexdocs) Overall very impressive.
2
GKinif
Hello,
I started reading the book a couple of weeks ago (unfortunately not a lot of time in the evening).
I am currently in Chapter 6 about Authorization, specifically the part “Writing Policies for Albums”.
When adding the “created_by” and “updated_by” attributes, there is a note about adding a policy in the user resource in order for actors to read their own records, allowing to populated the 2 fields.
Before adding the policy I tried without it to see what kind of error it would show and if I would understand it.
Unfortunately when I tried, I did not found any errors in my terminal so wanted to know if I was missing something.
Step to reproduce:
I enabled Policy debugging in my dev config as recommended in the book
# Enable policies debugging in development
config :ash, :policies, show_policy_breakdowns?: true
- Make sure there the policy for users to read their own record is removed
- Create a new artists => works
- Navigate to the artist details page (show_live)
- Click the edit button
- Try to change the artist name => fail
- Put back the policy
- Try to update the name again => works
Here is the log I received in the terminal:
"SAVE: %{\"biography\" => \"qsdsqdsq\", \"name\" => \"test3 2\"}"
[debug] HANDLE EVENT "save" in TunezWeb.Artists.FormLive
Parameters: %{"form" => %{"biography" => "qsdsqdsq", "name" => "test3 2"}}
[debug] QUERY OK db=1.9ms idle=1043.2ms
begin []
↳ anonymous fn/3 in Ash.Changeset.with_hooks/3, at: lib/ash/changeset/changeset.ex:3695
[debug] QUERY OK source="artists" db=6.5ms
SELECT a0."id", a0."updated_by_id" FROM "artists" AS a0 WHERE (a0."id"::uuid::uuid = $1::uuid::uuid) ["05a9fb89-74da-4bcc-913b-b12a1f59c2c7"]
↳ anonymous fn/3 in AshPostgres.DataLayer.run_query/2, at: lib/data_layer.ex:785
[debug] QUERY OK db=4.7ms
rollback []
↳ anonymous fn/3 in Ash.Changeset.with_hooks/3, at: lib/ash/changeset/changeset.ex:3695
[debug] Replied in 26ms
My liveview does show an error notification, but without much details.
Is there an information I am missing from the logs?
0