Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

GraphQL: Accessing another resolver/field output from a sibling resolver

need some help. Let say Im requesting the following data:

{
  parent {
    obj1    {
        value1
    }
    obj2    {
        value2
    }
  }
}

And I need the result of value2 in value1 resolver for calculation.

Thought of returning a promise in in value2 and somehow take it in value1 resolver, but what if value2 resolver didn’t run yet?

There`s any way it could be done?

like image 854
alonp99 Avatar asked Jan 11 '17 17:01

alonp99


2 Answers

My immediate thought is that you could use the context to achieve something like this. I'd imagine you could have a cache like object mixed with an event emitter to solve the race condition issue.

For example, assume we had some class

class CacheEmitter extends EventEmitter {

  constructor() {
    super();
    this.cache = {};
  }

  get(key) {
    return new Promise((resolve, reject) => {
      // If value2 resolver already ran.
      if (this.cache[key]) {
        return resolve(this.cache[key]);
      }
      // If value2 resolver has not already run.
      this.on(key, (val) => {
        resolve(val);
      });
    })
  }

  put(key, value) {
    this.cache[key] = value;
    this.emit(key, value);
  }
}

Then from your resolvers you could do something like this.

value1Resolver: (parent, args, context, info) => {
  return context.cacheEmitter.get('value2').then(val2 => {
    doSomethingWithValue2();
  });
}

value2Resolver: (parent, args, context, info) => {
  return doSomethingToFetch().then(val => {
    context.cacheEmitter.put('value2', val);
    return val;
  }
}

I haven't tried it but that seems like it may work to me! If you give it a shot, I'm curious so let me know if it works. Just for book keeping you would need to make sure you instantiate the 'CacheEmitter' class and feed it into the GraphQL context at the top level.

Hope this helps :)

like image 142
mparis Avatar answered Nov 07 '22 00:11

mparis


According to graphql-resolvers: "GraphQL currently does not support a field to depend on the resolved result of another field". Using an EventEmiter seems like a very off-spec way of achieving this. graphql-tools offers helper functions that allow you to compose resolvers in a number of ways that should help you.

like image 4
leanne1 Avatar answered Nov 06 '22 23:11

leanne1