Ash Framework Book - how to debug the actions

And this error

CleanShot 2025-03-30 at 16.34.24@2x1924×372 20.8 KB

Thanks for assisting me with this. I am new to Elixir and ash and will be using ash to build a multi tenant app that connects to an external api. Very impressed with ash so far.

Now I’m thinking: what about having mix ash.gen.change?

I’m here for it

and it’s here for you

Apologies for the necro but I have some related nitpicky feedback and I specifically remembered this thread because the lack of @impl trues was causing me some dissonance as well. Perhaps you already caught this but since it’s not a change/validation/calculation I wanted to point it out: For the installed_extensions example in Speeding things up with custom database indexes, it would be helpful to include @impl true there as well.

Thanks, Rebecca and Zach!

I’ve just added @impl true to all the generated functions in the Repo module after installing AshPostgres - installed_extensions/0, min_pg_version/0, and prefer_transaction?/0. Good call and thanks for that!

Hello @sevenseacat , @zachdaniel ,

Can you please let me know if you have a best suggestion for implementing dual control and data filters in authorization?
In most enterprise applications you need maker/checker for sensitive actions/functions , also some users could be authorized to do an action like read/write on filtered set of data of the resource like certain branch or city ,..etc
Also if you can let me know what integrates well with Ash for record audit and maybe sensitive data view?

Thanks

For a maker/checker pattern that is something that I would likely use something like ash_state_machine (or just a :state attribute), with separate actions for making and checking, and separate policies on those two actions, allowing the maker to make and the checker to check etc. Could, for instance, just have a policy forbidding the maker from also being the checker etc.

For authorizing reads/writes on filtered sets of data, see policies. They are built for this purpose and will filter reads and writes appropriately.

For record audit, do you mean like audit logs/trails? If so we have ash_paper_trail as a core extension that will track changes to a resource over time.

For sensitive data view, I’m thinking you mean providing partial access to records etc., which can be implemented using field policies

Thanks @zachdaniel ,

The audit refers to monitor some critical resources changes “usually configuration resources” so that we can go to some UI to identify old value/new value and who did the change right from the start.

The sensitive data refers to those encrypted fields or in payment domain something like clear card number could be viewed only by users who have the privileges to do so while others could see a hashed or encrypted value.

I took a look at ash_state_ma chine and it seems serving the logic for changing the resources values utilizing maker/checker but looking for a sample repository or project to check it further.
btw , when will have the last chapter of the book?