Using graphql-shield with data-loader

[MorganDavid]

Hello, this library has been great so far, however I've run into a performance problem that is proving difficult to solve.

I have this type in my shield definition:

export const isChallengeViewableFunc = async (
  challenge,
  _args,
  ctx,
): Promise<boolean> => {
   // I want to replace this call with a dataloader
    const fetchedChallenge = await !!Challenge.query().where({userId: ctx.user.id, challengeId:challenge.id}).withGraphFetched("joined");
// only return challenge user has joined.
return !!fetched.joined;
};

const isChallengeViewable = rule({ cache: "contextual" })(
  isChallengeViewableFunc
);

export const permissions = shield({
  Challenge: {
      "*": isAuthenticated,
      id: isChallengeViewable,
      name: isChallengeViewable,
      description: isChallengeViewable,
      // lots more fields with isChallengeViewable
    },
})

When I request 20 challenges, that db query gets ran (at least) 20 times. I have tried using data-loader in here, but the shield will not resolve all the rules in the type asynchronously (it always waits for one field to complete before evaluating the next). This means that the data-loader query always loads with only one key (so there's still lots of db queries).

for example, if I do this inside one of the rules,

      console.log("1. starting to sleep");
      await sleep(5000);
      console.log("2. finished sleep");

I would expect something like:

1. starting to sleep
1. starting to sleep
1. starting to sleep
2. finished sleep
2. finished sleep
2. finished sleep

but instead they appear synchronously (graphql-middleware logs them synchronously so I'm currently planning on putting the dataloaders in there and using context to pass them to shield rules)

Is there some config I can change to make this work or is this a limitation of the library?

Thanks!