This repository has been archived by the owner on Nov 19, 2024. It is now read-only.
GraphQL: Remove section from resolvers topic #7001
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
keharper
added
Internal Dev
dobooth
approved these changes
Apr 6, 2020
lenaorobei
approved these changes
Apr 6, 2020
Closed
4 tasks
|
running tests |
|
Hi @keharper, thank you for your contribution! |
|
@keharper The hand of fate has been dealt. You must add a section for |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
This pull request (PR) removes conflicting information about the general syntax of a mutation.
Affected DevDocs pages
whatsnew
Removed recommendations about defining separate types for input and output data in GraphQL resolvers.