Skip to content
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

enhance(ResolveFieldValue): note that list items may be async #1066

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

yaacovCR
Copy link
Contributor

@yaacovCR yaacovCR commented Dec 7, 2023

and some baseline collection language for comparison

extracted from #742

Copy link

netlify bot commented Dec 7, 2023

Deploy Preview for graphql-spec-draft ready!

Name Link
🔨 Latest commit 32053c0
🔍 Latest deploy log https://app.netlify.com/sites/graphql-spec-draft/deploys/66eb2ba856279f0008d32e04
😎 Deploy Preview https://deploy-preview-1066--graphql-spec-draft.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@yaacovCR
Copy link
Contributor Author

yaacovCR commented Dec 7, 2023

@graphql/tsc -- I think this could count as an editorial change? It is currently implemented within graphql-js on main as part of the incremental delivery alpha/beta, has not been released...

benjie
benjie previously requested changes Dec 7, 2023
Copy link
Member

@benjie benjie left a comment

Choose a reason for hiding this comment

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

Please restore the paragraph breaks which will both minimise the diff and restore the formatting of the note (which has special handling in spec-md).

@yaacovCR
Copy link
Contributor Author

yaacovCR commented Dec 7, 2023

Please restore the paragraph breaks which will both minimise the diff and restore the formatting of the note (which has special handling in spec-md).

Done, thanks!

spec/Section 6 -- Execution.md Outdated Show resolved Hide resolved
and some baseline collection language for comparison

extracted from graphql#742

Authored-by: Rob Richard <rob@1stdibs.com>
Copy link
Member

@benjie benjie left a comment

Choose a reason for hiding this comment

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

Minor wording suggestions

spec/Section 6 -- Execution.md Outdated Show resolved Hide resolved
spec/Section 6 -- Execution.md Outdated Show resolved Hide resolved
Copy link
Member

@benjie benjie left a comment

Choose a reason for hiding this comment

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

Looks good to me, and despite being non-normative this already aligns with the behavior of GraphQL.js. I think we can flag this as an editorial note.

@benjie benjie added the ✏️ Editorial PR is non-normative or does not influence implementation label Sep 19, 2024
@benjie
Copy link
Member

benjie commented Sep 19, 2024

@graphql/tsc This PR extends the non-normative note about resolvers being asynchronous to also note that each entry in a list returned from a resolver can itself be asynchronous. Please either approve or express your concerns - thanks!

@benjie benjie changed the title enhance(ResolveFieldValue): add async collection language enhance(ResolveFieldValue): note that list items may be async Sep 19, 2024
@fotoetienne fotoetienne self-requested a review September 19, 2024 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✏️ Editorial PR is non-normative or does not influence implementation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants