-
Notifications
You must be signed in to change notification settings - Fork 1.2k
res.json fails to work properly when json response is too large #744
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
mathieuartu opened this issue
Dec 16, 2014
· 1 comment
· May be fixed by xblaster/generator-angular-fullstack#17, xblaster/generator-angular-fullstack#18, xblaster/generator-angular-fullstack#19, xblaster/generator-angular-fullstack#20 or xblaster/generator-angular-fullstack#30
Closed
res.json fails to work properly when json response is too large #744
mathieuartu opened this issue
Dec 16, 2014
· 1 comment
· May be fixed by xblaster/generator-angular-fullstack#17, xblaster/generator-angular-fullstack#18, xblaster/generator-angular-fullstack#19, xblaster/generator-angular-fullstack#20 or xblaster/generator-angular-fullstack#30
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I've been experiencing problems with json and generator-angular-fullstack recently.
Try it for yourself : just add a large amount of "things" into the seed.js file via the Thing.create({...}) function, then try to display it via http://localhost/api/things.
You'll notice that at some point there's the end of the JSON "]" and then its starts again right away "[".
I've tested it in 3 different environments and still can reproduce the bug.
I don't think the amount of data is too large since it should be a able to display hundreds of things and not be limited to somewhat approximately 90 items.
Do you guys know about this, and is there a workaround ? Thanks !
The text was updated successfully, but these errors were encountered: