mockzilla/com.apadmi.mockzilla.lib.internal.utils

Package-level declarations

Types

AddressAlreadyInUseException

actual typealias AddressAlreadyInUseException = BindException

expect class AddressAlreadyInUseException : Throwable

actual typealias AddressAlreadyInUseException = PosixException.AddressAlreadyInUseException

actual typealias AddressAlreadyInUseException = DummyException

actual typealias AddressAlreadyInUseException = BindException

class DummyException : IOException

JsMockzillaRequest

class JsMockzillaRequest(jsRequest: Request) : MockzillaHttpRequest

KtorMockzillaHttpRequest

class KtorMockzillaHttpRequest : MockzillaHttpRequest

Properties

isProbablyRunningOnEmulator

val isProbablyRunningOnEmulator: Boolean

Functions

isSomeMatchInChain

fun Throwable.isSomeMatchInChain(predicate: (Throwable) -> Boolean): Boolean

noOpConfigBuilder

fun noOpConfigBuilder(noop: MockzillaConfig.Builder)

For some infuriating reason, nested classes defined in dependent modules don't automatically have headers generated unless they're being used within the module. This usage forces the generation of the headers.

setDefaultHandlerCallback

fun setDefaultHandlerCallback(builder: EndpointConfiguration.Builder, block: (request: MockzillaHttpRequest, (MockzillaHttpResponse) -> Unit) -> Unit)

setErrorHandlerCallback

fun setErrorHandlerCallback(builder: EndpointConfiguration.Builder, block: (request: MockzillaHttpRequest, (MockzillaHttpResponse) -> Unit) -> Unit)

setPatternMatcherCallback

fun setPatternMatcherCallback(builder: EndpointConfiguration.Builder, block: (request: MockzillaHttpRequest, (Boolean) -> Unit) -> Unit)