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
EasyLocalization is currently tightly coupled to EasyLogger. This is an issue for apps that want to use a different logger, or want to log to something other than the console (for example Firebase Crashlytics or Sentry).
The only way around this limitation right now is to customize EasyLocalization.logger.printer, but that still relies on EasyLogger.
I suggest creating a callback parameter (e.g. onEvent) in EasyLocalization that by default passes the events to EasyLogger for compatibility. The internal easyLocalization code should then call this new onEvent parameter instead of EasyLocalization.logger; perhaps using some private helper function that is similar to the existing logging methods.
This approach would allow users to use any logging framework that they want, without having to go through EasyLogger.
The text was updated successfully, but these errors were encountered:
This issue is based on an idea mentioned in #374.
EasyLocalization
is currently tightly coupled toEasyLogger
. This is an issue for apps that want to use a different logger, or want to log to something other than the console (for example Firebase Crashlytics or Sentry).The only way around this limitation right now is to customize
EasyLocalization.logger.printer
, but that still relies onEasyLogger
.I suggest creating a callback parameter (e.g.
onEvent
) inEasyLocalization
that by default passes the events toEasyLogger
for compatibility. The internal easyLocalization code should then call this newonEvent
parameter instead ofEasyLocalization.logger
; perhaps using some private helper function that is similar to the existing logging methods.This approach would allow users to use any logging framework that they want, without having to go through
EasyLogger
.The text was updated successfully, but these errors were encountered: