CacheMap.get calls should await the promised value
Author: gabidiCreated Oct 31, 2022Updated Jun 13, 2025
Seems like this prevents the use of async calls to centralized caches in it's current implementation since the returned promise will be 'Truthy' even if it resolves with a cache miss (null, undefined).
Wondering if there is a design reason for this, or a PR is welcome ?
Source: graphql/dataloader