Skip to content

Type validation from graphql.0 #7

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

Closed
wants to merge 4 commits into from
Closed

Conversation

olegrok
Copy link
Collaborator

@olegrok olegrok commented Mar 26, 2020

@olegrok olegrok requested a review from Totktonada March 26, 2020 14:49
@olegrok olegrok closed this in #9 Feb 25, 2021
no1seman added a commit to no1seman/graphql that referenced this pull request Mar 26, 2021
no1seman added a commit to no1seman/graphql that referenced this pull request Mar 29, 2021
olegrok pushed a commit that referenced this pull request Mar 29, 2021
According to http://spec.graphql.org/draft/#sec-Errors executor
must be able to return data or errors or data and errors.

Сloses #11
DifferentialOrange pushed a commit that referenced this pull request Nov 15, 2021
32c97f0 introduced returning data and errors acc. spec #7.1.2 but
previous implementation didn't take into account that execution may
include multiple resolvers and each of them may return both data and
errors. This PR fixes the logic to collect all errors from all resolvers
into a single map that can be returned to requester.

Based on PR #19 by @no1seman
DifferentialOrange pushed a commit that referenced this pull request Nov 18, 2021
32c97f0 introduced returning data and errors acc. spec #7.1.2 but
previous implementation didn't take into account that execution may
include multiple resolvers and each of them may return both data and
errors. This PR fixes the logic to collect all errors from all resolvers
into a single array that can be returned to requester.

Based on PR #19 by @no1seman
Totktonada pushed a commit that referenced this pull request Nov 18, 2021
32c97f0 introduced returning data and errors acc. spec #7.1.2 but
previous implementation didn't take into account that execution may
include multiple resolvers and each of them may return both data and
errors. This PR fixes the logic to collect all errors from all resolvers
into a single array that can be returned to requester.

Based on PR #19 by @no1seman
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant