Resource's DSL "metric" actions
Hi @Zach Daniel,
related to yesterday's question (supportHow to make simple select count with Ash) I got a new hint: we're trying a full-spread ash adoption on our internal project and we're trying to use only resource's code-interfaces everywhere, but for yesterday
What about the idea of a new kind of action supported by ash resource's DSL for defining resource's metrics methods in a declarative way?
For example on a
Going forward we could think about a more widely
All this actions could then be declared within the resources's code_interface.
I think this new kind of actions could be an useful feature on all ash extension (graphql, json, ...)
related to yesterday's question (supportHow to make simple select count with Ash) I got a new hint: we're trying a full-spread ash adoption on our internal project and we're trying to use only resource's code-interfaces everywhere, but for yesterday
count/1 I've to call api module directly.What about the idea of a new kind of action supported by ash resource's DSL for defining resource's metrics methods in a declarative way?
For example on a
User resource we can declare a simple metric :daily_subscribers action applying some logic and filters that returns a count of that metric.Going forward we could think about a more widely
metric :subscribers_growth action accepting a period argument that let us select a specific time window for that metric.All this actions could then be declared within the resources's code_interface.
I think this new kind of actions could be an useful feature on all ash extension (graphql, json, ...)
