Skip to content

docs: anatomy of a resolver #4381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 3, 2025

Conversation

sarahxsanders
Copy link
Contributor

adds anatomy of a resolver guide

This is a part of the effort to expand GraphQL.js documentation

@sarahxsanders
Copy link
Contributor Author

Thanks for approving :) Feel free to merge whenever! @saihaj let me know if there is a specific process to get merge permissions

@JoviDeCroock JoviDeCroock merged commit e6cd9fc into graphql:16.x.x May 3, 2025
17 checks passed
JoviDeCroock pushed a commit that referenced this pull request May 4, 2025
adds anatomy of a resolver guide

This is a part of the effort to expand GraphQL.js documentation
- Use context effectively. Store shared per-request information, such as
authentication data or database connections, in the `context` object rather
than passing it manually between resolvers.
- Prefer batching over nested requests. For fields that trigger multiple
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prefer batching over nested requests.

It's not totally clear to me what this sentence means?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants