The issues #1618 and #1625 will define the requirements for an (SDK user-provided) object that receives log output from the SDK and is responsible for writing it to some sort of output.
This issue aims to define the API of this object as an Objective-C protocol.
Next steps
In #1620 we’ll create the protocol which will implement this interface. Initially its interface will be similar to that of ARTLog. In #1621, we’ll create an adapter implementation of this protocol, which writes its output to a given ARTLog instance.
After that, as the requirements of #1618 and #1625 become clearer, we’ll split this task into tasks that update the protocol to satisfy these requirements.
1631 suggests writing mini-libraries that attempt to integrate this interface with some commonly-used logging libraries. This will help us validate that this interface is fit for purpose.
Background
The issues #1618 and #1625 will define the requirements for an (SDK user-provided) object that receives log output from the SDK and is responsible for writing it to some sort of output.
This issue aims to define the API of this object as an Objective-C protocol.
Next steps
In #1620 we’ll create the protocol which will implement this interface. Initially its interface will be similar to that of
ARTLog
. In #1621, we’ll create an adapter implementation of this protocol, which writes its output to a givenARTLog
instance.After that, as the requirements of #1618 and #1625 become clearer, we’ll split this task into tasks that update the protocol to satisfy these requirements.
1631 suggests writing mini-libraries that attempt to integrate this interface with some commonly-used logging libraries. This will help us validate that this interface is fit for purpose.
┆Issue is synchronized with this Jira Task by Unito