-
-
Notifications
You must be signed in to change notification settings - Fork 363
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
Provide an option to remove "errors" tab #88
Comments
@ColtonIdle |
Yep. Basically to only have the original functionality of chuck. Which is to inspect network traffic because I already use other tools for errors. |
I see. As a side note: Chucker is not capturing crashes unless you explicitly call |
I'll create PR after #98 is merged. |
Would like to return to this question. I haven't seen much feedback or requests about error reporting feature since I joined the team, so it just gives some points to my suggestion of removing this functionality at all and making Chucker focused on network only. I believe that it is better to focus on something specific in such tool and do it great. |
I'm also in for removing it. Maybe we want to loop in with @olivierperez since he initially developed it. Are you actually using this feature? I would love to understand what's the adoption rate of it. |
Hi, I'm ok too. This feature seems to be unused. |
Pool is a great idea. Let's do it :) |
I'd rather create a poll as a Github Issue as the majority of our users are there. We can set the issue as sticky and have a deadline say 2/3 weeks. People can vote using reactions like: 👍 Let's keep the feature |
@cortinico Ok, I will create such issue. But I also would like to ask you to also post the link to tbis issue in Twitter, since your account is the most popular among us. |
Sure let's do that 👍 |
Closing this one due to deprecation of |
I use a few other crash reporters and crash viewers built into my application. The fact that Chucker added this onto Chuck is nice, but I want to get rid of it so my team doesn't get confused about whether or not we should be using it vs our other error reporters. During Chucker setup, it'd be nice to just opt-out of having the error feature showing/working.
The text was updated successfully, but these errors were encountered: