chucker: Poll about `Errors` tab future
Hey everyone.
Chucker evolves pretty fast and becomes better every day thanks to great feedback from the community and contributors hard work. However, there are some features that don’t get much feedback on possible improvements. One such feature is ability to capture Throwable errors and show them in Errors tab. Moreover there are even some suggestions asking to disable that tab or remove it completely (like in #88 or here).
While it looks reasonable that Chucker could remove this feature completely and focus just on network part we don’t know for sure if this feature is used a lot or everyone just ignores it. Since there is no analytics available we would like to create sort of a poll in this issue and see your opinion.
To vote just put a reaction to this message with emoji.
Available options are:
👍 - Leave Errors tab and errors collection feature.
👎 - Remove Errors tab and errors collection feature.
This poll is valid for 1 month till May 8th so we could gather enough feedback.
We would also love to hear your feedback on whenever you or your team used/use Errors tab and if it was/is helpful, so don’t hesitate to leave comments here, in this issue.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 42
- Comments: 20 (6 by maintainers)
@Shipaaaa As previously mentioned here https://github.com/ChuckerTeam/chucker/issues/321#issuecomment-624132984, we can dump all the code for the Error feature in a self isolated module and make it available as a separate library/module if there is demand for it.
It just seems to me like chucker should stick to doing what it does well and what it was created to do. Networking.
I’ve got other libraries for crashes.
Another example. Charles proxy doesn’t try to catch my errors either. 😄
I also think it is a usable and useful feature but it is not about usability and usefulness. There are multiple other features that could be done here as well. Screenshot capture, logs preview, and so on. This does not mean that they should exist in this library. Even the description does not indicate that Chucker is a general-purpose tool -
An HTTP inspector for Android & OkHTTP. Otherwise, how would you distinguish between what belongs to the library and what doesn’t?In the end, it’s up to the authors and this poll but I don’t see why this should stay. Single responsibility principle can and should be applied on a library level as well. In my opinion Chucker’s responsibility is
I want to inspect network calls.@Shipaaaa as mentioned above, you can use Hyperion. https://github.com/willowtreeapps/Hyperion-Android
Hello! I missed this poll. This feature is very useful and helpful for QA and beta testing. It’s easier and faster to open the Chunker than to connecting the phone to the ADB or to finding the crash in the Crashlytics. Maybe you can recommend alternative proven solutions?
We are closing our poll as the deadline reached. The option for removing Errors tab got more votes. Adding a screenshot from the moment of writing this message to fix the result.
Errors tab won’t go right away. For the
3.3.0release all the parts connected with it will be declared as deprecated, so everyone will be aware of coming changes.Complete removal is expected in
4.xrelease.Yes, correct.
Just to add to the discussion, I recently wrote a small article about the 2 use cases I found for Chucker, one is of course to log network traffic but the other is to log Uncaught exceptions with a custom crash handler. It’s really useful mainly for testers, having both features in only one tool is something that helps a lot, so should you choose to focus on network logs please leave a way (maybe in settings) to enable it for people that find this useful: https://itnext.io/log-uncaught-exceptions-and-network-traffic-with-chucker-for-android-ps-967fe3e0488c?source=friends_link&sk=71105759bd2316d8f5cc420c4dc7d5a7