zachdaniel:

I’ve pushed a change to main to have all unsent notifications while in a transactions stored in the process dictionary by default, and then sent by the internal engine after the transaction completes. Now the only time you will need to gather up notifications is if you are manually starting and stopping transactions using Ash.DataLayer.transaction . So in your resource changes, for example, you can get rid of return_notifications? . Seems like a pretty big ergonomics boost to me 😄

kernel_io:

the notifiers will still trigger though right?

zachdaniel:

yes 🙂

kernel_io:

great improvement to get rid of another possible foot gun

kernel_io:

🙂

zachdaniel:

although someone is reporting an issue with it so may need to fix it

zachdaniel:

Okay, fixed 🙂