-
Notifications
You must be signed in to change notification settings - Fork 2k
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
incremental: use filtering instead of GraphQLResult #4043
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for compassionate-pike-271cb3 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @yaacovCR, I'm @github-actions bot happy to help you with this PR 👋 Supported commandsPlease post this commands in separate comments and only one per comment:
|
3565b37
to
7fb50bd
Compare
use-undefined-for-empty corresponds to #4046 the above stats show that with filtering, we have significant performance boost for synchronous lists, and we have maintained parity even for asynchronous lists |
7fb50bd
to
5c427d1
Compare
5c427d1
to
1633e92
Compare
introducing separate looping functions for when streamUsage is defined
1633e92
to
e5c9a71
Compare
now that filtering has been removed from #4026, this draft PR could be checked out to see what it would look like to reintroduce it.