congrats! good call on avoiding burn-out 🙏

For this, it looks like you're adding one extra field per agg function you are supporting:

did you consider something like sumRating: sum("rating") instead?

(Asking because I did something similar for a different case (filters), and now I kind of regret it)

Thanks @U08JKUHA9. TBH, I went this way after trying with different approaches. I did consider this sum("rating") but this resulted in

sum("rating") {
  value
}

I do agree the field per aggregate function is not the cleanest way but I had no other better option

Love to receive your inputs / suggestions that’y I am keeping this library in alpha state and building it in public

interesting, why did it result in returning an object instead of a scalar?

Thanks a ton @U08JKUHA9 I just checked the GraphQL schema https://graphql.org/learn/schema/#arguments. It is possible to have arguments on fields. My Bad, I was thinking only it applies to queries and get carried along on.

I will fix it in the next release. Thanks again :)

yea this may be a good case for it, if you want to avoid the potential field "explosion"

np 🙂

Created an issue to keep track of it https://github.com/graphqlize/graphqlize/issues/57