You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In network section, the Response section which actually is the most important part is too hard to access.
For some device especially the built in emulator, due to smaller screen length, the Response Section is unexposed at bellow.
We then had to scroll to make the Response section visible, and then click it to view it.
I don't know but this toke too much effort in my opinion.
The step to get the information that i need is to much.
Need to click pluto, open network section, open the request , scroll down, click the body section.
It tooks alot of time, and effort.
I used to use Chucker before, and im happy how fast i can access the information that i needed.
Describe the solution you'd like
i have some ideas; the simplest is to bring the Response section Up to the top.
Another is to show more widget that provides the "Catching list". the catch don't need tobe specific. Put everything in one list, for network, ANR, crashes etc, its fine. It also good to give different color accent for each context
then add filter option on it, such network only, crash etc. this extra widget can then become a single purpose debugger via filtering it.
we can debug network only and can skip all step above make it faster to access.
It will be more awesome if the extra widget can show counter of new Catches. especially exception and error.
This counter really is the main purpose of debugger, that to inform us that something wrong is happen.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In network section, the Response section which actually is the most important part is too hard to access.
For some device especially the built in emulator, due to smaller screen length, the Response Section is unexposed at bellow.
We then had to scroll to make the Response section visible, and then click it to view it.
I don't know but this toke too much effort in my opinion.
The step to get the information that i need is to much.
Need to click pluto, open network section, open the request , scroll down, click the body section.
It tooks alot of time, and effort.
I used to use Chucker before, and im happy how fast i can access the information that i needed.
Describe the solution you'd like
i have some ideas; the simplest is to bring the Response section Up to the top.
Another is to show more widget that provides the "Catching list". the catch don't need tobe specific. Put everything in one list, for network, ANR, crashes etc, its fine. It also good to give different color accent for each context
then add filter option on it, such network only, crash etc. this extra widget can then become a single purpose debugger via filtering it.
we can debug network only and can skip all step above make it faster to access.
It will be more awesome if the extra widget can show counter of new Catches. especially exception and error.
This counter really is the main purpose of debugger, that to inform us that something wrong is happen.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: