graphql/dataloader

[QUESTION] Is possible chain two dataloaders?

Open

#229 opened on Nov 20, 2019

View on GitHub
 (1 comment) (3 reactions) (0 assignees)JavaScript (12,520 stars) (556 forks)batch import
help wanted

Description

Hi, is it possible chain two dataloaders? I have one resolver where I need using two dataloaders, is it possible? I can't use SQL join because it's slow.

async (row, _, { dataSources }) => {
    const partialData = await dataloader1(dataSources).load(row.id);
    if (partialData === null) {
        return null;
    }
    return await dataloader2(dataSources).load(partialData.id);
}

Contributor guide

Tech stack
javascriptgraphql
Domain
backendapi
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with DataLoaderJavaScript async/await
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue asks if it's possible to chain two dataloaders. To verify, one can examine the DataLoader API and write a simple test using successive load() calls. The existing examples in the repository's README or the test file (e.g., src/ tests /dataloader.test.js) may provide confirmation. A comment from maintainers or the community could clarify the intended usage pattern.