Allow GraphQL endpoint to return larger responses#2533
Merged
ludovicm67 merged 1 commit intomainfrom Mar 4, 2026
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
hupf
approved these changes
Mar 4, 2026
Contributor
hupf
left a comment
hupf
left a comment
There was a problem hiding this comment.
We have to keep in mind that this can increase the RAM usage of the Next.js application. But I guess do to the Linked Data nature of those GraphQL queries, we cannot take them apart...
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR increase the response limit from 4 MB to 20 MB for the GraphQL endpoint.
This should solve some cases where the response were too huge to create visualizations.