-
Notifications
You must be signed in to change notification settings - Fork 497
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
Improve our logging system #4351
Labels
Comments
stefanceriu
added a commit
that referenced
this issue
Jun 1, 2021
stefanceriu
added a commit
that referenced
this issue
Jun 2, 2021
stefanceriu
added a commit
that referenced
this issue
Jun 2, 2021
stefanceriu
added a commit
to matrix-org/matrix-ios-kit
that referenced
this issue
Jun 2, 2021
stefanceriu
added a commit
to matrix-org/matrix-ios-kit
that referenced
this issue
Jun 2, 2021
Replace NSLog with MXLog - element-hq/element-ios/issues/4351
stefanceriu
added a commit
that referenced
this issue
Jun 3, 2021
…g() and replaced more print() usages with MXLog.debug()
stefanceriu
added a commit
that referenced
this issue
Jun 3, 2021
* Adopted the new MXLog and replaced NSLog throughout the application - /issues/4351 * Replaced NSLog() and print() usages with MXLog.debug() * Added swiftlint rules for NSLog(), print(), println() and os_log() * Escape paths used to run script build phases for swiftlint and swiftgen
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to have a more advanced logging system than the basic
NSLog()
in MatrixSDK, MatrixKit, Element-iOS where:debug()
everywhere during the transition step and affine latter.NSLog(@"[MyClass] xxxx")
to separate them. This is boring to repeat[MyClass]
on every logWe should have a weak dependency on the logging lib we will use. We could probably reuse the MXLogger object.
The text was updated successfully, but these errors were encountered: