Oh okay, that actually makes it a lot clearer to understand.
I guess my only question left would be is if there’s a recommended way to organize multiple preparations for a single Ash Resource.
In the real world case at work, we’d probably be using a lot of Ash.Query.load and Ash.Query.after_action for getting the results of many different aggregates or calculations and changing the shape of the data in order to properly display it in places, so keeping all of those functions group in the same module would be useful.
