mirror of
https://github.com/vale981/apollo-server
synced 2025-03-04 17:21:42 -05:00
![]() In an effort to maintain consistency and semantically correct meaning, this changes (only in documentation and internal Apollo Server tests) the name of the first argument in resolver signatures to use `parent` rather than `root`. While `root` certainly makes sense when the resolver is belonging to the root `Query` or `Mutation` type, once nested field resolvers begin getting called, the more semantically correct term would seem to be `parent`. Since `parent` still makes sense at the root level, and since resolvers frequently get copied and pasted into more deeply-nested positions, putting this pattern in place for apps which are just beginning might just help someone more clearly understand the relationship in the future — without incorrectly thinking that a nested resolver is accessing the root of the graph, rather than the parent. |
||
---|---|---|
.. | ||
apollo-cache-control | ||
apollo-datasource | ||
apollo-datasource-rest | ||
apollo-engine-reporting | ||
apollo-engine-reporting-protobuf | ||
apollo-server | ||
apollo-server-azure-functions | ||
apollo-server-cache-memcached | ||
apollo-server-cache-redis | ||
apollo-server-caching | ||
apollo-server-cloud-functions | ||
apollo-server-cloudflare | ||
apollo-server-core | ||
apollo-server-env | ||
apollo-server-errors | ||
apollo-server-express | ||
apollo-server-hapi | ||
apollo-server-integration-testsuite | ||
apollo-server-koa | ||
apollo-server-lambda | ||
apollo-server-micro | ||
apollo-server-plugin-base | ||
apollo-server-testing | ||
apollo-tracing | ||
graphql-extensions |