optimizely / optimizely-flutter-sdk / 18754800486

87%

push

github

[FSSDK-11853] add swift logger support (#88)

* build: add Optimizely SDK logger classes

- Add FlutterOptimizelyLogger class implementing OPTLogger protocol
- Add constants for customLogger and loggerChannel
- Implement FlutterMethodChannel for invoking log method
- Add logger field to OptimizelyFlutterSdk constructor
- Initialize custom logger in OptimizelyClientWrapper
- Create LoggerBridge to handle log method calls
- Implement OptimizelyLogger interface and DefaultOptimizelyLogger class

* fix: resolve logging inconsistencies

- Update custom logger initialization in OptimizelyFlutterSdkPlugin
- Adjust logger channel setup in onDetachedFromEngine
- Refactor LoggerBridge to handle log calls from native Swift/Java code properly
- Ensure proper logging when no custom logger is set

* refactor: update logger imports

- Rename 'OptimizelyLogger.dart' to 'flutter_logger.dart'
- Rename 'LoggerBridge.dart' to 'logger_bridge.dart'
- Modify imports in 'optimizely_client_wrapper.dart' to reflect changes in logger files

* feat: add custom logger implementation

- Implement a custom logger class
- Define logLevel property with default debug level
- Define log method to print log messages with custom format

* refactor: rename logger classes in Android and iOS

- Rename FlutterOptimizelyLogger to OptimizelyFlutterLogger in Android
- Rename FlutterOptimizelyLogger to OptimizelyFlutterLogger in iOS

* feat: update logging behavior for Optimizely SDK

- Remove unused log level property in CustomLogger
- Implement channel setter method in OptimizelyFlutterLogger
- Add guard clauses for levels and logger channel availability in log method
- Update channel invocation to happen on main thread
- Set log level in SwiftOptimizelyFlutterSdkPlugin based on parameters
- Simplify DefaultOptimizelyLogger log method
- Update log message formatting in logger bridge for consistency

* feat: add methods and tests for logger state management

- Add methods to expose converting l... (continued)

41 of 47 new or added lines in 3 files covered. (87.23%)

661 of 777 relevant lines covered (85.07%)

1.37 hits per line