debugger-client/pro.respawn.flowmvi.debugger.client/debuggerPlugin

debuggerPlugin

fun <S : MVIState, I : MVIIntent, A : MVIAction> debuggerPlugin(client: HttpClient, timeTravel: TimeTravel<S, I, A>, host: String = DebuggerDefaults.ClientHost, port: Int = DebuggerDefaults.Port, reconnectionDelay: Duration = DebuggerDefaults.ReconnectionDelay): LazyPlugin<S, I, A>

Creates a new remote debugging plugin.

  • You must also provide a TimeTravel for the plugin to use where it will track events.

  • This overload uses a custom client for networking. This client must be configured to correctly serialize and use websockets for connection. See the documentation to learn how to set up the client. If you want to use the default client, depend on debugger-plugin module instead.

This plugin must not be used in production code. Better yet, do not include the debugger-client dependency at all in production builds, because the plugin depends on a lot of things you may not need for your application.

fun <S : MVIState, I : MVIIntent, A : MVIAction> debuggerPlugin(client: HttpClient, historySize: Int = DefaultHistorySize, host: String = DebuggerDefaults.ClientHost, port: Int = DebuggerDefaults.Port, reconnectionDelay: Duration = DebuggerDefaults.ReconnectionDelay): LazyPlugin<S, I, A>

Creates a new remote debugging plugin.

  • This overload will create and install a TimeTravel plugin for you.

  • This overload uses a custom client for networking. This client must be configured to correctly serialize and use websockets for connection. See the documentation to learn how to set up the client. If you want to use the default client, depend on debugger-plugin module instead.

This plugin must not be used in production code. Better yet, do not include the debugger-client dependency at all in production builds, because the plugin depends on a lot of things you may not need for your application.