Closed vazarkevych closed 1 month ago
Any reason not to use Slf4j (as proposed in https://github.com/growthbook/growthbook-sdk-java/pull/24) so that users can pick whatever logging backend they want (including java logging) ?
I can only support @igorlovich. The SDK is now highly coupled to the java based logging implementation. That would mean that every consumer/user of the SDK has to provide additional configuration to change the message format or other properties, although they might have these configuration already in place - but for the logging framework that they have in use, like Log4j or Logback. Using SLF4J would avoid all these conflicts.
So, we need to add SLF4J
printStackTrace() was replaced with logging