Apollo GraphQL 服务器中的别名字段

Question

Aliasing is very handy and works great when aliasing a specific resolver. For instance:

{
  admins: users(type:"admin"){
    username
  }
  moderators: users(type:"moderators"){
    moderators
  }
}

I'm not sure how to handle aliasing of the fields themselves though. For example:

{
  site_stats {
    hits: sum(field: "hits")
    bounces: sum(field: "bounces")
  }
}

If the resolver returns any sum value, the same value is aliased to both hits and bounces (which makes sense, since only a single sum value could even be returned). If I make the resolver use the alias names as the field names when returning the results, hits and bounces both become null .

I could simply break those fields out into separate resolvers, but that complicates integration for the front end devs. We would also lose a ton of efficiency benefits, since I can aggregate all the data needed in a single query to our data source (we're using ElasticSearch).

Any help from you geniuses would be greatly appreciated!

Answer 1

It sounds like you're putting all your logic inside the root-level resolver ( site_stats ) instead of providing a resolver for the sum field. In other words, if your resolvers look like this:

const resolvers = {
  Query: {
    site_stats: () => {
      ...
      return { sum: someValue }
    },
  },
}

you should instead do something like:

const resolvers = {
  Query: {
    site_stats: () => {
      return {} // empty object
    },
  },
  SiteStats: {
    sum: () => {
      ...
      return someValue
    },
  },
}

This way you're not passing down the value for sum from the parent and relying on the default resolver -- you're explicitly providing the value for sum inside its resolver. Since the sum resolver will be called separately for each alias with the arguments specific to that alias, each alias will resolve accordingly.

Answer 2

Using aliases and single fields has very limited usability.

You can use complex filters (input params), fe list of keys to be returned and their associated params, fe

[{name:"hits", range:"month"}, 
{name:"bounces", range:"year"}]

With query - expected structure

{
  stats {
    name
    sum
    average
  }
}

Required fields may vary, fe only name and sum .

You can return arrays of object fe

{ stats: [
  { name:"hits", 
    sum:12345, 
    average: 456 }

Aliases can be usable here to choose different data sets fe name and sum for hits , bounces additionally with average .

... more declarative?

PS. There is nothing that "complicates integration for the front end devs". Result is json, can be converted/transformed/adapted after fetching (clinet side) when needed.