fix: update how debug logging works #174
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only logged invocation coming from the SDK that matches the logging level defined by the customer will be printed to Logcat.
The idea here is to have the customer supply the lowest level that they want to get logs for -- they would do that in the
create
function where we now default toLoggingLevel.WARN
.The SDK is then opinionated about which level to log different things on, for example:
Warnings and errors can contain message from a
throwable
.