Hotwire.config.makeCustomWebView conflicts with Hotwire.registerBridgeComponents()

[joemasilotti]

Using both Hotwire.config.makeCustomWebView and Hotwire.registerBridgeComponents() causes unexpected behavior. If the web view is configured first then it is not used. If bridge components are registered first then the bridge is not initialized in the web view.

It's not uncommon for developers to need to do both. Disabling link previews, for example, requires access to the underlying web view.

Hotwire.config.makeCustomWebView = { config in
    let webView = WKWebView(frame: .zero, configuration: config)
    webView.allowsLinkPreview = false
    return webView
}

Currently, a developer must choose between bridge components or a custom web view.

This is happening because Hotwire.registerBridgeComponents() overwrites Hotwire.config.makeCustomWebView to initialize the bridge.