Throw a "data too large" error in ListMapper when parsing data bigger than a certain size like 100MB #15780
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.
Why
When the response size is large like in the support case in WOOMOB-607 with a large amount of product metadata, the UI could become unresponsive. Other than moving the response parsing to a background thread, the client can also prevent the app from taking up unexpectedly large amount of device resources in case of receiving exceedingly large data.
TODO: still figuring out a way to show appropriate error UX, and maybe disable max size check by default.
Description
Steps to reproduce
Testing information
Screenshots
RELEASE-NOTES.txt
if necessary.