Why would you need to use
after_actionto display loaded data?
Sorry, I worded that wrong.
after_action wouldn’t be for displaying data, we would use it for a read action to transform the data. So for certain API endpoints we can just called Ash.Api.get! or whichever function to call the read action, and that way we can limit the logic in endpoints.
Like a service in Spring that specifically gets data an endpoint will send out contains most of the logic to transform the data, as opposed to doing it in the endpoint itself.
EDIT: But I do see your point on generic actions
