Closed ernestask closed 2 years ago
This isn’t ideal in that cbindgen only reads Cargo.toml for features, so separate cargo-build and cbindgen invocations might result in the header still exposing the setter, but it’s more than likely that there will only be one user of this.
@antonok-edm, would be great if you could take a peek and let me know if this is close to what you had in mind.
Currently, the bindings require client code to set an external domain resolver, which can be cumbersome, as the embedded one suffices. This commit adds a feature that enables embedded-domain-resolver in adblock-rust and conditionally hides the setter from the bindings.
Related: https://github.com/brave/adblock-rust-ffi/issues/35