infrastructure tier

infrastructure-whatsapp-bridge

WhatsApp adapter via HTTP bridge — read and send messages through the browser extension

WhatsApp adapter via HTTP bridge — read and send messages through the browser extension

Tierinfrastructure
Roleunclassified (baselined)
Pathcrates/infrastructure/whatsapp-bridge
Edition2021
Targetsinfrastructure_whatsapp_bridge
Public items0 across 0 modules
Tests15

What it is for

WhatsApp adapter via HTTP bridge.

Connects to the WhatsApp browser extension bridge and provides an async API for listing chats, reading messages, and sending messages.

Uses HTTP POST to /api/extension-command instead of direct CDP.

Capabilities

No public items.

How to use it

No examples/ target and no doctest in this crate's rustdoc. The tests listed under Verification are the closest executable usage.

Module structure

No public modules: the crate root is its whole surface.

Public surface

No public items.

Re-exports. Exported here, defined elsewhere.

ExportDefined in
WhatsAppBridgeErrorerror::WhatsAppBridgeError
{BridgeConfig,Chat,Message,MessageDirection,SendResult,WhatsAppBridge}client::{BridgeConfig,Chat,Message,MessageDirection,SendResult,WhatsAppBridge}

Boundary

Depends on no other workspace tier.

Shares tier infrastructure with 82 other crates: infrastructure-acquire, infrastructure-adapters-google-calendar, infrastructure-adapters-google-gmail, infrastructure-adapters-google-places, infrastructure-adapters-google-trends, infrastructure-adapters-shodan, infrastructure-adapters-yelp, infrastructure-agent, … (82 total).

_What this crate deliberately does NOT own is a judgment. No committed registry records one for it, so none is stated here._

Where it sits

Tier (ontology)infrastructure
Architectural role (taxonomy)unclassified (baselined)
Locationcrates/infrastructure/whatsapp-bridge
Vocabulary in force (lexicon)current

Dependencies

Runtime, in this workspace.

CrateTierOptionalOnly on
`infrastructure-fetcher`infrastructurenoalways

Runtime, from outside the workspace.

CrateRequirementFeaturesOptionalOnly on
reqwest^0.12jsonnoalways
serde^1derivenoalways
serde_json^1noalways
thiserror^2noalways
tracing^0.1noalways

Development. None.

Build. None.

Depended on by. 1 workspace crate.

Signal flow — what reaches this crate, and what it reaches.

flowchart LR
  n_application_whatsapp_bridge["application-whatsapp-bridge"] -->|uses| SELF
  SELF["infrastructure-whatsapp-bridge"]
  SELF -->|runtime| n_infrastructure_fetcher["infrastructure-fetcher"]
  classDef self fill:#1f883d,stroke:#1f883d,color:#fff;
  class SELF self;

Feature flags

No Cargo features are defined: every capability is unconditional, so no consumer can receive a half-wired crate.

Targets

KindNameSource
libinfrastructure_whatsapp_bridge`src/lib.rs`

Error model

No public error type was detected: no public item declares a type named *Error, and no public signature returns one.

Operational characteristics

PropertyEvidence
async public surfacenone detected
async runtimenone detected
database accessnone detected
network I/Oyes
unsafe codenone detected
environment variablesyes

No unsafe block, unsafe fn, unsafe impl or unsafe trait was found by the parser anywhere in this crate's source.

Configuration

VariableRead in
BRIDGE_API_KEYsrc/client.rs
BRIDGE_TIMEOUT_SECSsrc/client.rs
BRIDGE_URLsrc/client.rs

1 workspace crate depends on this one: application-whatsapp-bridge.

Verification

KindCount
Unit tests15
Integration tests0
Examples0
Doctests0

What the tests establish, by name:

Documentation coverage

MeasureDocumentedTotal
Public items with rustdoc00
Public modules with a //! block00

Metrics

MetricValue
Rust source files3
Source lines567
Code lines436
Public API items0
Public modules0
Tests15
Examples0
Cargo features0
Direct runtime dependencies6
Workspace reverse dependencies1
pie showData
    title Rust source composition
    "Code" : 436
    "Blank or comment" : 131

Generation

Rendered by tools-corpus corpus readme from repository evidence alone, renderer schema 2, lexicon current. No model, network service or database was consulted. Regenerate with tools-corpus corpus readme --write; verify with --check.

All infrastructure · Manual