MartinVolerich
I’m still not 100% with my understanding of the JSON_API layers on Ash.
I’ve created an easy and working aggregate to count the number of related (to_many) records on a resource.
But… I’d like to insert that aggregate value into the JSON api response for gets & reads. I’m currently doing that using the previously learned metadata approach - but I’m curious whether there is a better way to do this.
While I’m at it… Are aggregates the best way to go or should I be using some other form of calculated attributes instead.
Thanks
Martin
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
Ah, so metadata is not necessary for this.
You can use the
fieldsquery parameter to include public aggregates (i.e aggregates withpublic?: true. For examplefields[type]=agg_name,other,fields. If you want the aggregate to be included by default, you can setdefault_fieldson therouteor the resource level, i.eThat will make them appear as standard attributes in the response.
MartinVolerich
That’s perfect. Many thanks. The trick (at least to me) was to make the aggregate public and to add it manually to he fields list - or fall back (with no fields list) to the default_fields list.
Thanks again. I’m slowly getting there - step by step.
Martin