-
Notifications
You must be signed in to change notification settings - Fork 5
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
feat: support changing loggers at runtime WPB-11541 #747
Conversation
a067908
to
b7d6bc0
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #747 +/- ##
==========================================
- Coverage 72.12% 72.05% -0.07%
==========================================
Files 106 106
Lines 19718 19737 +19
==========================================
Hits 14222 14222
- Misses 5496 5515 +19
Continue to review full report in Codecov by Sentry.
|
b7d6bc0
to
7132e83
Compare
@typfel this is a breaking change, right? |
I kept the old API around in the wrapper but for iOS it would be a breaking change. I can fix that though. |
7132e83
to
34e78cd
Compare
Currently it's only allowed to set a logger and log level once at runtime, this restriction is annoying for clients since they setup and teardown the core crypto stack when switching accounts. It also makes it harder than it should be to have developer setting for increasing the core crypto log level.
34e78cd
to
d7a83f4
Compare
I've re-introduced the old API and re-named the new API. old: In the next release where we break the API we'll delete old method and rename the new API. |
What's new in this PR
Support changing loggers and max log level at runtime.
also renamed
initLogger
in the bindings tosetLogger
since IMO init is not suitable anymorewhen we allow replacing a logger.
PR Submission Checklist for internal contributors
SQPIT-764
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.