Allow null throwable when logging errors

[JcMinarro]

🎯 Goal

There are some cases where we want to log an error but the exception/throwable can be null, in that case, an if-else check needs to be done before logging this error. The StreamLog already handles this case internally.

Imagine the following class:

data class Error(
  val message: String,
  val throwable: Throwable? = null
)

With previous implementation, we would have something like:

fun handleError(error: Error) {
  if (error.throwable != null) {
    logger.e(error.throwable) { error.message }
  } else {
    logger.e { error.message }
  }
  [...]
}

That can be changed by:

fun handleError(error: Error) {
  logger.e(error.throwable) { error.message }
  [...]
}

[VelikovPetar]

Looks good!
We should just make sure that the new version would be compatible with the older ones. Ex:

• integrator uses the newest (unreleased) version
• Chat/Video are on a different older version of log

[JcMinarro]

Looks good! We should just make sure that the new version would be compatible with the older ones. Ex:

• integrator uses the newest (unreleased) version
• Chat/Video are on a different older version of log

I think it should because previous methods are maintained and even we reduce restrictions (nullable values is less restricted than non-nullable values)

[VelikovPetar]

Looks good! We should just make sure that the new version would be compatible with the older ones. Ex:

• integrator uses the newest (unreleased) version
• Chat/Video are on a different older version of log

I think it should because previous methods are maintained and even we reduce restrictions (nullable values is less restricted than non-nullable values)

Let's just test this scenario before updating the Chat/Video SDKs to use the newer version!