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
In previous version (3.0.0) we used .loggable(BuildConfig.DEBUG) for logging network log only for DEBUG build. Right now (in 3.1.0 version) this method is deprecated and suggested to replace this method with .setLevel(Level.BASIC).
Is this .setLevel(Level.BASIC) method ensure logging only in DEBUG build?
I've tested using this method in release build. Still network log is showing in console (for testing purpose I made debuggable true for release build).
What is your recommended way to ensure LOGGING in debug build and NOT LOGGING in release build?
The text was updated successfully, but these errors were encountered:
BASIC logs url, method, headers and body as you can see in this link https://github.com/ihsanbal/LoggingInterceptor#level
Yeah I know loggable was more useful for different build variants but setLevel provides more flexibility to developers. I can recommend you to use something like below.
Firstly, thanks a lot for your awesome library.
In previous version (3.0.0) we used
.loggable(BuildConfig.DEBUG)
for logging network log only for DEBUG build. Right now (in 3.1.0 version) this method is deprecated and suggested to replace this method with.setLevel(Level.BASIC)
.Is this
.setLevel(Level.BASIC)
method ensure logging only in DEBUG build?I've tested using this method in
release
build. Still network log is showing in console (for testing purpose I madedebuggable true
for release build).What is your recommended way to ensure LOGGING in debug build and NOT LOGGING in release build?
The text was updated successfully, but these errors were encountered: