Currently the tool uses LocalStorage and Chrome Storage to store all successful service responses.
This is a useful feature but it's unreasonable to store responses that, in some cases, are well over 1MB. This can cause tools designed to read Chrome Storage to crash.
If feasible, responses over a certain size (e.g. 200KB), shouldn't be stored.
Currently the tool uses LocalStorage and Chrome Storage to store all successful service responses.
This is a useful feature but it's unreasonable to store responses that, in some cases, are well over 1MB. This can cause tools designed to read Chrome Storage to crash.
If feasible, responses over a certain size (e.g. 200KB), shouldn't be stored.