fix: logger instance, consistent param naming
fix: initialize library logger instance on client creation so that it is available immediately for purpose chore(deps): add akkurate for parameter validation (future work) refactor: all option field names to clearly identify them as user-configurable chore(deps): update kotlin to 2.1.0, ktor, serialization, coroutines, koin to support refactor: expose kermit as classpath dependency so loggers can be directly instantiated by consumers
Showing
- gradle/libs.versions.toml 10 additions, 8 deletionsgradle/libs.versions.toml
- temerity/build.gradle.kts 1 addition, 1 deletiontemerity/build.gradle.kts
- temerity/src/commonMain/kotlin/edu/ucsc/its/temerity/TemClientConfig.kt 17 additions, 18 deletions...ommonMain/kotlin/edu/ucsc/its/temerity/TemClientConfig.kt
- temerity/src/commonMain/kotlin/edu/ucsc/its/temerity/core/Temerity.kt 13 additions, 9 deletions.../commonMain/kotlin/edu/ucsc/its/temerity/core/Temerity.kt
- temerity/src/commonMain/kotlin/edu/ucsc/its/temerity/di/LibModule.kt 3 additions, 3 deletions...c/commonMain/kotlin/edu/ucsc/its/temerity/di/LibModule.kt
- temerity/src/jvmTest/kotlin/edu/ucsc/its/temerity/test/DevUtilityTests.kt 15 additions, 9 deletions...Test/kotlin/edu/ucsc/its/temerity/test/DevUtilityTests.kt
- temerity/src/jvmTest/kotlin/edu/ucsc/its/temerity/test/ProdUtilityTests.kt 21 additions, 8 deletions...est/kotlin/edu/ucsc/its/temerity/test/ProdUtilityTests.kt
Loading
Please register or sign in to comment