As described in #1618, there are some logging solutions that SDK users might commonly be using (e.g. Logger, OSLog). Part of the aim of #1618 and #1628 is to create a public logging API that allows users to take full advantage of the functionality offered by these libraries, and to use them in a manner consistent with their applications’ / libraries’ current use of these APIs.
We may wish to go a step further and actually create some mini libraries for logging to these log handlers. This will allow us to:
validate that our public logging API is fit for purpose
reduce time and effort spent by our users on implementing this
If in #1627 we decide to log to OSLog, then here we might just need to do this for Logger.
Background
As described in #1618, there are some logging solutions that SDK users might commonly be using (e.g.
Logger
,OSLog
). Part of the aim of #1618 and #1628 is to create a public logging API that allows users to take full advantage of the functionality offered by these libraries, and to use them in a manner consistent with their applications’ / libraries’ current use of these APIs.We may wish to go a step further and actually create some mini libraries for logging to these log handlers. This will allow us to:
If in #1627 we decide to log to
OSLog
, then here we might just need to do this forLogger
.┆Issue is synchronized with this Jira Task by Unito