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/1What 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
Usermetric :daily_subscribersGoing forward we could think about a more widely
metric :subscribers_growthperiodAll 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, ...)
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.
2,193Members
Resources
Similar Threads
Was this page helpful?
