Cargo Features

[dependencies]
timezynk-bridge-models = { version = "0.1.4", default-features = false, features = ["client", "server", "conversion"] }
default = client, server

These default features are set whenever timezynk-bridge-models is added without default-features = false somewhere in the dependency tree.

client default = hyper, hyper-tls, native-tls, openssl, serde_ignored, tokio-core, url

Affects timezynk-bridge-models::client

server default = hyper, hyper-tls, native-tls, openssl, percent-encoding, regex, serde_ignored, tokio-core, tokio-proto, tokio-tls, url

Affects timezynk-bridge-models::server

conversion = frunk, frunk-enum-core, frunk-enum-derive, frunk_core, frunk_derives

Features from optional dependencies

In crates that don't use the dep: syntax, optional dependencies automatically become Cargo features. These features may have been created by mistake, and this functionality [may be removed in the future](https://rust-lang.github.io/rfcs/3491-remove-implicit-features.html).

hyper client server

Enables hyper ^0.11

Crates included if required by the API definition

Common between server and client features

hyper-tls client server

Enables hyper-tls ^0.1.2

native-tls client server

Enables native-tls ^0.1.4

openssl client server

Enables openssl ^0.9.14

serde_ignored client server

Enables serde_ignored ^0.0.4

tokio-core client server
url client server

Enables url ^1.5

percent-encoding server

Enables percent-encoding ^1.0.0

Client-specific


Server-specific

regex server

Enables regex ^0.2

tokio-proto server
tokio-tls server

Enables tokio-tls ^0.1.3

frunk conversion?

Enables frunk ^0.3.0

Other optional crates

frunk_derives conversion?

Enables frunk_derives ^0.3.0

frunk_core conversion?

Enables frunk_core ^0.3.0

frunk-enum-derive conversion?

Enables frunk-enum-derive ^0.2.0

frunk-enum-core conversion?

Enables frunk-enum-core ^0.2.0