Resolver iku fungsi sing ngasilake nilai kanggo siji field ing schema. GraphQL mlaku ing query field mbaka field lan nyeluk resolver sing cocog kanggo saben field — mlaku iku sing diarani resolver chain.
Saben resolver nampa (parent, args, context, info):
User nalika ngresolve user.posts).{ id: "1" }).const resolvers = {
Query: {
// top-level: parent is undefined; read args, use context for data access
user: (_parent, args, ctx) => ctx.db.users.findById(args.id),
},
User: {
// runs for EACH user; parent is the resolved user object
posts: (parent, _args, ctx) => ctx.db.posts.findByAuthor(parent.id),
// no resolver needed for 'name' -> the default resolver reads parent.name
},
};
Yen sawijining field ora duwe resolver eksplisit, GraphQL nganggo default resolver sing mung maca parent[fieldName]. Kuwi sebabe field scalar ing object biasa lumrahe ora perlu kode.
Mangerteni yen resolver mlaku saben field, saka ndhuwur mudhun, ngetutake parent chain njlentrehake carane data nested dirakit lan uga kenapa resolver nested sing naif nyebabake masalah N+1 — pitakon lanjutan wawancara sing alami.
Pustaka pitakon wawancara IT kanthi jawaban rinci — saka Junior nganti Senior.
Nyumbang