-
Notifications
You must be signed in to change notification settings - Fork 72
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
Remove response limit from fides.js #4878
Remove response limit from fides.js #4878
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
…onse-Size-Limited-to-4MB-error-when-generating-large-fides.js-responses
Passing run #7690 ↗︎
Details:
Review all test suite changes for PR #4878 ↗︎ |
…onse-Size-Limited-to-4MB-error-when-generating-large-fides.js-responses
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works as expected! I added a long description to one of the banner descriptions and I was able to create a payload over 4MB in size from fides.js
. The error doesn't actually prevent the download but removing this limit eliminates this false alarm that might cause concern for some users.
Closes #PROD-2031
Description Of Changes
By default Next.JS throws "API Routes Response Size Limited to 4MB" when the response is larger than 4MB, disabling this will not throw data in the console. But this can allow us to have very big responses without noticing anymore. From the Next.JS docs: API Routes in Next.js are designed to deliver quick responses and are not built to support the transmission of large amounts of data.
Code Changes
config
variable tofides-js.ts
to change theapi.responseLimit
tofalse
Steps to Confirm
script
variable onfides-js.ts
file to include a lot of comments, just 4MB of it, and you'll get a message on the dev web server shell. After this change gets into main, the message will be gone.Pre-Merge Checklist
CHANGELOG.md