Is there a more idiomatic way to have a wrapper around an Ht kotlinlang #ktor

Channels

100daysofkotlin

100daysofkotlin-2021

algolialibraries

android-architecture

android-databinding

androidgithubprojects

androidx-xprocessing

arrow-contributors

beepiz-libraries

cincinnati-user-group

codemash-precompiler

codingconventions

competitive-programming

competitivecoding

compose-android

compose-desktop

compose-ui-showcase

connect-audit-events

cscenter-course-2016

domain-driven-design

effective-kotlin

effectivekotlin

embedded-kotlin

event21-community-content

fb-internal-demo

fluid-libraries

framework-elide

getting-started

github-workflows-kt

graviton-browser

image-processing

intellij-plugins

intellij-tricks

introduce-yourself

java-to-kotlin-refactoring

jhipster-kotlin

jvm-ir-backend-feedback

k2-early-adopters

kotest-contributors

kotlin-by-example

kotlin-data-storage

kotlin-foundation

kotlin-in-action

kotlin-multiplatform-contest

kotlin-pakistan

kotlinforbeginners

kotlingforbeginners

kotlinprogrammers

kotlintest-devs

kotlinultimatechallenge

kotlinx-datetime

lambdaworld_cadiz

language-evolution

language-proposals

leedskotlinusergroup

library-development

machinelearningbawas

myndocs-oauth2-server

navigation-architecture-component

ohio-kotlin-users

pattern-matching

pocketgitclient

practical-functional-programming

prozis-android-backup

python-contributors

realworldkotlin

refactoring-to-kotlin

refreshversions

russian-kotlinasfirst

skia-wasm-interop-temp

sofl-user-group

spring-security

squarelibraries

stayhungrystayfoolish

strife-discord-lib

swagger-gradle-codegen

swiss-user-group

tricity-kotlin-user-group

Title

p

Paul Griffith

02/17/2021, 6:51 PM

Is there a more idiomatic way to have a wrapper around an HttpClient that sets up some default features, but also allows some use-site customization? More in a thread, but basically I want to be able to create an

XClient

which might be backed by a

CIOEngine

...but also be able to use the same class but with a

MockEngine

, which requires being able to add handlers

I've got an abstract class like this

Then impl classes look like this (adding additional features)

Which then allows customization at the use site like this:

But the stuff at the abstract class feels very weird and unergonomic

Guess I answered my own question, making the second parameter on the abstract class

engineCustomization: EngineType.() -> Unit = {},

which then makes the client initialization

protected val client: HttpClient by lazy {    HttpClient(clientSupplier.create(engineCustomization), clientConfiguration)
}

makes things a lot nicer to look at

Just kidding, that can even be reduced further, because HttpClientEngineFactory has a

create

extension function, so you don't need to provide a configuration lambda at all

#ktor Join Slack