Skip to content

Conversation

@UntitledMoose
Copy link

Hey y'all,

Would you consider switching to the Android Log utility instead of println, since the print statements can clutter logcat output and make debugging harder? This allows teams to filter out Panels debug statements more easily with a logcat rule (-tag:PANELS) in Android Studio, rather than having to disable them altogether with Panels.INSTANCE.getConfig().setEnableLogs(false).

Thanks so much!

TLDR: Replaced println statements in the log and error methods with Log.d and Log.e respectively, using a consistent TAG for all log messages to enable logcat filtering

@UntitledMoose
Copy link
Author

@MonsieurLazar Just a quick reminder ping!

@Froze-N-Milk
Copy link

would be even better to use the RobotLog sdk log wrapper

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants